From d753ad59fde12d4dd01c52f9dc5a41e635caf2d5 Mon Sep 17 00:00:00 2001 From: plf Date: Mon, 14 May 2018 06:48:48 -0700 Subject: C++: Renames CcCompilationContextInfo to CcCompilationContext Since it's not a provider, it doesn't need the Info suffix anymore. RELNOTES:none PiperOrigin-RevId: 196498526 --- .../com/google/devtools/build/lib/rules/cpp/FdoSupport.java | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'src/main/java/com/google/devtools/build/lib/rules/cpp/FdoSupport.java') diff --git a/src/main/java/com/google/devtools/build/lib/rules/cpp/FdoSupport.java b/src/main/java/com/google/devtools/build/lib/rules/cpp/FdoSupport.java index ea6dddc02b..0a1223f98a 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/cpp/FdoSupport.java +++ b/src/main/java/com/google/devtools/build/lib/rules/cpp/FdoSupport.java @@ -116,12 +116,12 @@ import java.util.zip.ZipFile; * .gcda files are added, too. * * - *

If we do LIPO, the actual {@code CcCompilationContextInfo} for LIPO compilation actions is - * pieced together from the {@code CcCompilationContextInfo} in LipoContextProvider and that of the - * rule being compiled. (see {@link CcCompilationContextInfo#mergeForLipo}) This is so that the - * include files for the extra LIPO sources are found and is, strictly speaking, incorrect, since it - * also changes the declared include directories of the main source file, which in theory can result - * in the compilation passing even though it should fail with undeclared inclusion errors. + *

If we do LIPO, the actual {@code CcCompilationContext} for LIPO compilation actions is pieced + * together from the {@code CcCompilationContext} in LipoContextProvider and that of the rule being + * compiled. (see {@link CcCompilationContext#mergeForLipo}) This is so that the include files for + * the extra LIPO sources are found and is, strictly speaking, incorrect, since it also changes the + * declared include directories of the main source file, which in theory can result in the + * compilation passing even though it should fail with undeclared inclusion errors. * *

During the actual execution of the C++ compile action, the extra sources also need to be * include scanned, which is the reason why they are {@link IncludeScannable} objects and not simple -- cgit v1.2.3