-
Notifications
You must be signed in to change notification settings - Fork 13.4k
libprofiler_builtins: Set compilation flags more correctly for C code. #60402
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
libprofiler_builtins: Set compilation flags more correctly for C code. #60402
Conversation
@bors: r+ |
📌 Commit d52fde2 has been approved by |
…-build, r=alexcrichton libprofiler_builtins: Set compilation flags more correctly for C code. In particular, set `COMPILER_RT_HAS_FCNTL_LCK` and `COMPILER_RT_HAS_ATOMICS` as appropriate. This should get rid of the various runtime warnings when executing instrumented binaries. The build script is using a heuristic here that hopefully is sufficient for the time being. r? @alexcrichton Fixes rust-lang#59531.
Failed in #60420 (comment) . |
@bors r- ^ |
d52fde2
to
d4dfbeb
Compare
Typo fixed. @bors r=alexcrichton |
📌 Commit d4dfbeb has been approved by |
…-build, r=alexcrichton libprofiler_builtins: Set compilation flags more correctly for C code. In particular, set `COMPILER_RT_HAS_FCNTL_LCK` and `COMPILER_RT_HAS_ATOMICS` as appropriate. This should get rid of the various runtime warnings when executing instrumented binaries. The build script is using a heuristic here that hopefully is sufficient for the time being. r? @alexcrichton Fixes rust-lang#59531.
⌛ Testing commit d4dfbeb with merge c3b08da044476a942cf78b3b4fc67d943a5890be... |
💔 Test failed - status-appveyor |
I was able reproduce this locally. It seems that Clang 7 can't handle some of the C instrinsics for Arm64 Windows yet. Switching to Clang 8 fixes the problem. @rust-lang/infra, how would I update the clang version defined here? Lines 152 to 164 in 55c48b4
|
Ok I've uploaded the 8.0.0 binary to our CI bucket, if you update s/7/8/g here I think it should work |
❤️ |
In particular, set COMPILER_RT_HAS_FCNTL_LCK and COMPILER_RT_HAS_ATOMICS as appropriate.
d4dfbeb
to
0ffc573
Compare
Clang version updated. @bors r=alexcrichton |
📌 Commit 0ffc573 has been approved by |
⌛ Testing commit 0ffc573 with merge 9bee31424656ffbdc627226a394857a8aeb80ff9... |
@bors retry |
…lexcrichton libprofiler_builtins: Set compilation flags more correctly for C code. In particular, set `COMPILER_RT_HAS_FCNTL_LCK` and `COMPILER_RT_HAS_ATOMICS` as appropriate. This should get rid of the various runtime warnings when executing instrumented binaries. The build script is using a heuristic here that hopefully is sufficient for the time being. r? @alexcrichton Fixes #59531.
☀️ Test successful - checks-travis, status-appveyor |
Tested on commit rust-lang/rust@3f5152e. Direct link to PR: <rust-lang/rust#60402> 💔 rls on windows: test-pass → test-fail (cc @Xanewok, @rust-lang/infra). 🎉 rls on linux: test-fail → test-pass (cc @Xanewok, @rust-lang/infra).
It landed I'm wondering how RLS could be affected by these changes... |
There's a spurious test in RLS 😓 |
Ah, OK. Thanks for the info, @kennytm! |
In particular, set
COMPILER_RT_HAS_FCNTL_LCK
andCOMPILER_RT_HAS_ATOMICS
as appropriate. This should get rid of the various runtime warnings when executing instrumented binaries.The build script is using a heuristic here that hopefully is sufficient for the time being.
r? @alexcrichton
Fixes #59531.