[PATCH] D131469: [Clang] change default storing path of `-ftime-trace`

Douglas Yung via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Fri Sep 2 19:23:45 PDT 2022


dyung added a comment.

In D131469#3768274 <https://reviews.llvm.org/D131469#3768274>, @dongjunduo wrote:

> In D131469#3768260 <https://reviews.llvm.org/D131469#3768260>, @dyung wrote:
>
>> The test you added is failing on the PS4 linux bot because the PS4 platform requires an external linker that isn't present. Is linking necessary for your test? Or can -S or even -c work instead to accomplish what you are trying to test?
>
> Yeah the new test case is designed to test the compiling jobs with a linking stage.
>
> Are there any options or measures to avoid this test running on the PS4?

You could mark it as XFAIL: ps4

Your change also seems to have possibly the same issue when run on our PS5 Windows bot:
https://lab.llvm.org/buildbot/#/builders/216/builds/9260

  $ ":" "RUN: at line 2"
  $ "z:\test\build\bin\clang.exe" "--driver-mode=g++" "-ftime-trace" "-ftime-trace-granularity=0" "-o" "Z:\test\build\tools\clang\test\Driver\Output/exe/check-time-trace" "Z:\test\llvm-project\clang\test\Driver\check-time-trace.cpp"
  # command stderr:
  clang: error: unable to execute command: program not executable
  clang: error: linker command failed with exit code 1 (use -v to see invocation)


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D131469/new/

https://reviews.llvm.org/D131469



More information about the cfe-commits mailing list