From 3f6c57b3a2c86444ce4be119f51578ab7198071e Mon Sep 17 00:00:00 2001 From: plf Date: Tue, 3 Apr 2018 08:40:03 -0700 Subject: C++: Rename CcCompilationInfo to CcCompilationContextInfo. This is done so that the name CcCompilationInfo can be used for the C++ provider that will wrap all providers for compilation, similar to JavaInfo in Java. RELNOTES:none PiperOrigin-RevId: 191445120 --- .../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 e86514e199..7f19208e98 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 CcCompilationInfo} for LIPO compilation actions is pieced - * together from the {@code CcCompilationInfo} in LipoContextProvider and that of the rule being - * compiled. (see {@link CcCompilationInfo#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 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. * *

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