This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/10392] [3.3/3.4 regression] [SH] optimizer generates faulty array indexing
- From: "marcus at mc dot pp dot se" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Sep 2003 09:58:14 -0000
- Subject: [Bug optimization/10392] [3.3/3.4 regression] [SH] optimizer generates faulty array indexing
- References: <20030413145600.10392.marcus@mc.pp.se>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10392
------- Additional Comments From marcus at mc dot pp dot se 2003-09-13 09:58 -------
Subject: Re: [3.3/3.4 regression] [SH] optimizer generates faulty array indexing
Two comments about this test case:
1) It does not SIGSEGV on NetBSD/dreamcast. The argument to use()
will point into the environment buffer, in my case it points to
"VENDOR=unknown". But as long as it actually segfaults on the
machine you're using to run these tests, I suppose that's ok...
2) Because func() never returns zero, the program always exits with
status _1_, not 0.