This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A gcc-cris bug?
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: "Dave Korn" <dk at artimi dot com>
- Cc: "'Richard Guenther'" <richard dot guenther at gmail dot com>, <gcc at gcc dot gnu dot org>, "'Diego Novillo'" <dnovillo at redhat dot com>, "'Tal Agmon'" <tal dot agmon at nsc dot com>
- Date: Wed, 6 Oct 2004 10:55:09 -0400
- Subject: Re: A gcc-cris bug?
- References: <NUTMEGK2p9sfn9HnGlP000002c5@NUTMEG.CAM.ARTIMI.COM>
On Oct 6, 2004, at 10:47 AM, Dave Korn wrote:
Maybe, but it does make -O3 unusable, doesn't it? I know it's meant
to be
'unsafe' and come with suitable health warnings, but this sort of bad
codegen just seems beyond coping with. If the tree-based inliner has
always
been similarly unreliable, well maybe it isn't a regression, but also
maybe
the inliner should just be disabled on the release branches ?
But for 2.95.x there was no tree based inliner so it has nothing to do
with the inliner at all but rather a loop optimization or something
else.
-- Pinski