[Bug middle-end/67857] New: noreturn + volatile results in wrong code

-end Assignee: unassigned at gcc dot gnu.org Reporter: karl at skomski dot com Target Milestone: --- On Linux/x86-64, GCC 5.2 (g++ -m32 -O1) optimizes this test into wrong code: Important is the volatile argument to Increment and __noreturn__ function in the if clause

[Bug middle-end/67857] noreturn + volatile results in wrong code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67857 --- Comment #3 from karl at skomski dot com --- Thanks for the fast answer and sorry for wasting your time :/ Am Montag, 5. Oktober 2015 schrieb pinskia at gcc dot gnu.org : > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67857 > > Andr