------- Comment #4 from davek at gcc dot gnu dot org 2010-01-11 19:07 ------- (In reply to comment #3) > (even without the __noreturn__?)
Yes, even without. > I think this may be actually two bugs, one is the noreturn which should set > current_function_returns_abnormally to true, so no warning. Another is that > the > function is not marked as never returning because of the infinite loop. Sounds right to me. Ok to leave them both under this one PR, or should we separate them? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42674
