[Bug c++/38045] New: floating point exception triggered incorrectly

: unassigned at gcc dot gnu dot org ReportedBy: cstankevitz at toyon dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38045

[Bug c++/38045] floating point exception triggered incorrectly

--- Comment #1 from cstankevitz at toyon dot com 2008-11-07 05:48 --- Created an attachment (id=16630) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16630&action=view) Source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38045

[Bug c++/38045] floating point exception triggered incorrectly

--- Comment #2 from cstankevitz at toyon dot com 2008-11-07 05:48 --- Created an attachment (id=16631) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16631&action=view) Preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38045

[Bug c++/38045] floating point exception triggered when it shouldn't be

--- Comment #3 from cstankevitz at toyon dot com 2008-11-07 05:50 --- BTW, the invalid floating point exception is not triggered in g++-4.1.2 (GCC) 4.1.2 (Gentoo 4.1.2 p1.1) -- cstankevitz at toyon dot com changed: What|Removed |Added

[Bug c++/38045] floating point exception triggered when it shouldn't be

--- Comment #5 from cstankevitz at toyon dot com 2008-11-07 07:01 --- I should have added... the three instances of crashing are on 64 bit OS. The gentoo example above: [EMAIL PROTECTED] ~/delete $ uname -a Linux crs 2.6.25-gentoo-r7 #17 SMP Sun Nov 2 12:50:21 PST 2008 x86_64 Intel(R

[Bug c++/38045] floating point exception triggered when it shouldn't be

--- Comment #8 from cstankevitz at toyon dot com 2008-11-07 07:44 --- Any recommendation on how to work around it with GCC 4.3.2? Seemingly unrelated code changes make it go away. Thanks - Chris. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38045

[Bug c++/46806] New: -O3 implies 0 <= 8 <= 7

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46806 Summary: -O3 implies 0 <= 8 <= 7 Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassig...@gcc.gnu.org

[Bug c++/46806] -O3 implies 0 <= 8 <= 7

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46806 --- Comment #2 from Chris Stankevitz 2010-12-05 02:47:51 UTC --- > 8 is out of range of the enum. I agree. Unfortunately, with -O3, 8 is reported as in the range.

[Bug c++/46806] -O3 implies 0 <= 8 <= 7

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46806 Chris Stankevitz changed: What|Removed |Added Attachment #22636|0 |1 is obsolete|

[Bug c++/46806] -O3 implies 0 <= 8 <= 7

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46806 --- Comment #7 from Chris Stankevitz 2010-12-05 18:11:55 UTC --- If I understand correctly, you are saying "The following is not a valid way to test whether a user-supplied int is withing the bounds of an enum:" if ( Eight >= static_cast(

[Bug c++/46806] -O3 implies 0 <= 8 <= 7

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46806 Chris Stankevitz changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|