-
Notifications
You must be signed in to change notification settings - Fork 14.9k
RuntimeLibcalls: Use get_host_tool_path for executables used in benchmark #153955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeLibcalls: Use get_host_tool_path for executables used in benchmark #153955
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
…mark Copied from what the llvm-shlib build is doing. This reverts commit 0b1b567.
647a78e
to
c10ce10
Compare
ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as buildbots are happy :) Let's see
I'm not entirely sure how get_host_tool_path works, but looking at other uses it seems it should.
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/11/builds/24222 Here is the relevant piece of the build log for the reference
|
Perhaps it should be guarded by |
In the previous versions I hoped that would be implicit based on the check for the built target, that way it's not dependent on the exact set of build options if they ever change |
I think the latest approach is the correct one. IIRC the previous attempts might have tried to execute a cross-built tool. |
…in benchmark (llvm#153955)" This reverts commit f3c9c6c. Fails fuschia bot.
Attempt 2 #159489 |
We're seeing failures from this chain of patches in the emscripten toolchain. It doesn't appear any of the follow ups have fixed it either.
|
Copied from what the llvm-shlib build is doing.
This reverts commit 0b1b567.