: unassigned at gcc dot gnu.org
Reporter: gcc at sjor dot sg
Target Milestone: ---
The following code will cause a -Wreturn-type warning to be emitted in the
'foo' function, even though 'foo' calls throw_exception_ which is marked
__attribute__((__noreturn__)).
: unassigned at gcc dot gnu.org
Reporter: gcc at sjor dot sg
Target Milestone: ---
Created attachment 41729
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41729&action=edit
Minimal test case
See attached code. Tested on Ubuntu's gcc 6.2.0, Debian's 6.3.0, Arch's 7.1.1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81410
--- Comment #1 from Sjors Gielen ---
This is on x86_64 by the way. Doesn't happen with -m32.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81410
--- Comment #3 from Sjors Gielen ---
A trivial workaround is put inside the first loop:
std::cout << "";
I suppose this prevents loop optimization by introducing potential side
effects.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81410
--- Comment #14 from Sjors Gielen ---
(In reply to Jakub Jelinek from comment #13)
> GCC 5 branch is being closed
Has there been a fix for this issue at all in a 5 branch release?
And, for the 6 branch, will there be a release with a fix for th
