diff options
| author |  Googler <noreply@google.com> | 2018-03-15 09:09:00 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-03-15 09:10:55 -0700 |
| commit | 6a0ac92a0938f141644411f12cb4e6e499684886 (patch) | |
| tree | 7a92076ff92e0e7d407d13957b5a4bf4ca608315 | |
| parent | 4c3098cfa6f00f90c7530b6f40d3e93062931c1d (diff) | |
Include object exec path in LTO Backend progress message
With only the filename the LTO Backend objects are hard to distinguish (i.e.
many files will share the same base filename, but have different paths.
Additionally, this change causes the target specific ".lto" or "shared.nonlto"
subdirectory to be included, which is useful for analysis.
RELNOTES: None
PiperOrigin-RevId: 189194070
| -rw-r--r-- | src/main/java/com/google/devtools/build/lib/rules/cpp/LtoBackendArtifacts.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/rules/cpp/LtoBackendArtifacts.java b/src/main/java/com/google/devtools/build/lib/rules/cpp/LtoBackendArtifacts.java index cb26f91b43..8c4fc757ce 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/cpp/LtoBackendArtifacts.java +++ b/src/main/java/com/google/devtools/build/lib/rules/cpp/LtoBackendArtifacts.java @@ -201,7 +201,7 @@ public final class LtoBackendArtifacts { builder.addOutput(objectFile); - builder.setProgressMessage("LTO Backend Compile %s", objectFile.getFilename()); + builder.setProgressMessage("LTO Backend Compile %s", objectFile.getExecPath()); builder.setMnemonic("CcLtoBackendCompile"); // The command-line doesn't specify the full path to clang++, so we set it in the |