-
Notifications
You must be signed in to change notification settings - Fork 48
Conversation
|
Ah, I hadn't updated my local copy of gcc to the latest. I can make it work, but only with http://bugzilla.gdcproject.org/show_bug.cgi?id=42 fixed. And that breaks a lot of other stuff with it. I'll get back in a while when I've done some triaging. |
|
And it is (more or less) working! At least the build failure is because of an error in the codegen, rather than an ICE. :-) |
|
Split out the more complex logic in #221. Now the change is rather trivial. |
3f218f9
to
589d691
Compare
|
I might finally be at the drum-roll moment... |
0e9fa45
to
448bd06
Compare
|
Three failed unittests, testsuite passes. This may be a sign that there may still be more cases that cause silent corruption of codegen as a result of this. |
|
That aren't caught by testsuite nor unittester, that is. |
|
Now passing the unittester. :-o |
74df46a
to
53dd148
Compare
|
It turned out that the frontend returns false from So I'm adjusting the condition in |
|
Passes! |
|
Nice work! Now I'll just have to port this to all other branches ;-) |
|
Looks like there's more to be done. I just updated to the latest snapshot, and get more ICE's relating to setting |
|
Maybe this is related: Failing test for GCC 5: ICE while compiling phobos: GCC 4.9/4.8 |
|
Nope, I get something other. I'd imagine that some things may need to be adjusted for older versions of GCC. |
This should fix the broken builds after updating to latest GCC snapshot. The test in sdtor has always been flaky because of this anyway. With this the compiler should now consistently generate the same code regardless of optimization level.