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: "dank at kegel dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Sep 2003 16:15: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 dank at kegel dot com 2003-09-16 16:15 -------
Unfortunately, I can't think of a safe and effective way to specify -m4 right in
the testcase.
I could restrict the testcase to sh*-*-* and avoid failing
non-SH processors, but what about SH processors that can't run code
compiled with -m4?
I could restrict the testcase to sh4-*-*, and specify -m4; that would
make the intent clear, but wouldn't have run the test when e.g.
http://mc.pp.se/dc/files/gcc3.3toolchain_local.tar.bz2 was built,
as that used target shl-unknown-netbsdelf1.6T.
Any opinions?