-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Re-enable has_thread_local
for i686-msvc
#123257
Conversation
These commits modify compiler targets. |
r? compiler |
Note that this is enabled for |
Sorry for the delay!
I suppose you're referring to #108089? The changes look reasonable (I've read a bit through older issues and PRs) but I'm not an expert on this. However I will r+ this unless you know of someone who might have a clearer picture of this and could quickly look over this. @bors rollup=never (may cause unclear regressions) |
Yeah, sorry. We were never able to come up with a good test for failures which makes "yeah, I think this should be ok now" based on vibes the best we can hope for. I'm well aware this is not great and hopefully in the (touch wood) unlikely event it fails again we can at least get a good test case out of it. |
@bors r+ |
Re-enable `has_thread_local` for i686-msvc A few years back, `has_thread_local` was disabled as a workaround for a compiler issue. While the exact cause was never tracked down, it was suspected to be caused by the compiler inlining a thread local access across a dylib boundary. This should be fixed now so let's try again.
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Seems spurious, considering this PR doesn't affect Linux @bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (f96442b): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 675.861s -> 676.802s (0.14%) |
These 2 benchmarks seem to be on tiny noise spikes as of late, this is obviously noise. @rustbot label: +perf-regression-triaged |
A few years back,
has_thread_local
was disabled as a workaround for a compiler issue. While the exact cause was never tracked down, it was suspected to be caused by the compiler inlining a thread local access across a dylib boundary. This should be fixed now so let's try again.