[Bug target/26463] -O2, -O3, -Os segment fault due to bad array index on ARM
--- Comment #5 from rearnsha at gcc dot gnu dot org 2009-10-14 14:16 --- Closing as presumed fixed. -- rearnsha at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||FIXED Target Milestone|--- |4.5.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26463
[Bug target/26463] -O2, -O3, -Os segment fault due to bad array index on ARM
--- Comment #4 from mikpe at it dot uu dot se 2009-05-03 20:05 --- (In reply to comment #3) Comment #2 indicates that there isn't a problem with a 4.x series compiler . I'd like some feedback if this problem exists today with a more recent version of the compiler. I can't reproduce the problem with either gcc-4.3.4 20090405 or gcc-4.4.1 20090428 on an armv5tel-unknown-linux-gnueabi system. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26463
[Bug target/26463] -O2, -O3, -Os segment fault due to bad array index on ARM
--- Comment #3 from ramana at gcc dot gnu dot org 2009-04-29 16:44 --- Comment #2 indicates that there isn't a problem with a 4.x series compiler . I'd like some feedback if this problem exists today with a more recent version of the compiler. -- ramana at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26463
[Bug target/26463] -O2, -O3, -Os segment fault due to bad array index on ARM
--- Comment #2 from mikpe at it dot uu dot se 2007-05-31 20:35 --- I cannot reproduce this bug with gcc-4.0.4, 4.1.2, or 4.2.0 on an armv5b-softvfp-linux machine. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26463
[Bug target/26463] -O2, -O3, -Os segment fault due to bad array index on ARM
--- Comment #1 from mikpe at csd dot uu dot se 2006-03-04 22:50 --- Created an attachment (id=10970) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10970action=view) Test case for PR26463 I can confirm this bug with both gcc-3.3.6 and gcc-3.4.5, on armv5b-linux. I've added a simple test case that instead of crashing due to the stack being clobbered, prints an error message and exits with 1 if the bug occurred. This is a very nasty error. A fix, even if only to disable some broken code in gcc, would be very welcome. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26463