https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92617
--- Comment #5 from Piotr Seweryn ---
Obviously there is no return statement and warning was issued, however endless
loop isn't the expected result, don't you agree? And falling-through to the
next piece of code is even worse, coze we are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92617
--- Comment #3 from Piotr Seweryn ---
Similar problem occurs when -O2 or -O3 is used, there is also an endless loop,
however different assembler code is generated. I can also provided appropriate
.ii and .s files for O2 and O3 case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92617
--- Comment #2 from Piotr Seweryn ---
Created attachment 47324
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47324=edit
Assembler file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92617
--- Comment #1 from Piotr Seweryn ---
Created attachment 47323
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47323=edit
Pre-processed file
++
Assignee: unassigned at gcc dot gnu.org
Reporter: piotr.seweryn at gmail dot com
Target Milestone: ---
Created attachment 47322
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47322=edit
Compilation process stderr output
Consider the following code:
#include
