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
fix Issue 5922 - inline assembler - referencing immutable variable va… #11605
Conversation
Thanks for your pull request, @WalterBright! Bugzilla references
Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + dmd#11605" |
415d79a
to
9fae696
Compare
The win32 Auto-Tester failure is recurrent. If you look at the log for the PRs that pass everywhere but not for W32 it's always the same problem. |
So might as well pull this, then, since the test failure is not relevant. |
Yes, especially since the problem seems to be a UB in optlink. |
Auto-merge toggled on |
Looks like I can't override and pull anymore. As for Optlink, it hasn't changed recently, so why is the test suddenly failing now? |
I've clicked to activate automerge directly in the web interface of the Auto-Tester. |
Auto-merge toggled off |
That should work from GH now. I forgot that using the Auto-Tester feature to merge is only useful when external CI fail. |
What should work and what is GH? Anyhow, the "Merge pull request" box is greyed out. |
What should work is the box that's greyed... It's possible that manual merge is disabled because the Auto-Tester is tagged as "required". So you have to amend+force push if you want to get the changes merged today. |
Yes, I disabled that a while ago as it regularly lead to broken stuff being merged and Andrei directly or pushing to master. I can still be done via the settings, but it's a bit harder now with the hope of it being used less often. Edit: It only applies to the two required CIs (Auto-Tester and DAutoTest) though. You can still merge over Buildkite failures. |
The link failure + timeout suggests an internal failure in Optlink which opens it's "Message box of death" |
If it's the optlink message box, it's definitely an optlink bug. It's possible an older optlink is running on that platform. If you could zip up the files that optlink is linking and email them to me, I can do some checks for simple causes. |
…lues fails
Switch to the more powerful constant folding code in the semantic routines.