[Bug c++/37096] New: conditional evaluation incorrect with -O3

2008-08-12 Thread erik dot moller at cycos dot com
-O3 -msse2) -- Summary: conditional evaluation incorrect with -O3 Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: erik dot

[Bug middle-end/37096] conditional evaluation incorrect with -O3

2008-08-18 Thread erik dot moller at cycos dot com
--- Comment #3 from erik dot moller at cycos dot com 2008-08-18 16:20 --- Created an attachment (id=16084) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16084&action=view) main() for the testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37096

[Bug middle-end/37096] conditional evaluation incorrect with -O3

2008-08-18 Thread erik dot moller at cycos dot com
--- Comment #4 from erik dot moller at cycos dot com 2008-08-18 16:20 --- Created an attachment (id=16085) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16085&action=view) the test case it's as minimal I could get it... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37096

[Bug middle-end/37096] conditional evaluation incorrect with -O3

2008-08-18 Thread erik dot moller at cycos dot com
--- Comment #5 from erik dot moller at cycos dot com 2008-08-18 16:22 --- the printf("shouldn't happen: %d\n", pAR[0]) happens when debug flags -O2 or -O3 and -msse2 are set. the printf("nz: %d\n", nZ); seems to do something awful... void fun(short *pAR)

[Bug middle-end/37096] conditional evaluation incorrect with -O3

2008-09-08 Thread erik dot moller at cycos dot com
--- Comment #6 from erik dot moller at cycos dot com 2008-09-08 10:54 --- bug is still in 4.3.2 -- erik dot moller at cycos dot com changed: What|Removed |Added

[Bug target/37096] conditional evaluation incorrect with -O3

2008-09-12 Thread erik dot moller at cycos dot com
--- Comment #9 from erik dot moller at cycos dot com 2008-09-12 11:33 --- true, -fno-strict-aliasing makes even -O3 work... I don't know about the liasing, the example is very simple, can that happen when the SSE2 intrinsics are involved? -- http://gcc.gnu.org/bug