This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: A gcc-cris bug?

From: Richard Guenther <richard dot guenther at gmail dot com>
To: Dave Korn <dk at artimi dot com>
Cc: Diego Novillo <dnovillo at redhat dot com>, Tal Agmon <tal dot agmon at nsc dot com>, gcc at gcc dot gnu dot org
Date: Wed, 6 Oct 2004 14:48:17 +0200
Subject: Re: A gcc-cris bug?
References: <1097064169.26172.25.camel@localhost.localdomain> <NUTMEGG14dvQO3I9EOl000002b3@NUTMEG.CAM.ARTIMI.COM>
Reply-to: Richard Guenther <richard dot guenther at gmail dot com>

>   Heh, yeh, I was able to infer from Andrew's source listing that it wasn't
> going to take long to execute! :)
> 
>   Hmm.  Bad timing in the release cycle to bring this up though.  Might be
> worth looking at in time for 3.3.6, though, would be nice to knock it on the
> head before the branch gets closed.

Might be not a regression.  2.95.2 and 3.0 behave the same, i.e. use
-O2 -finline-functions,
or simpler put an inline before f.  Somebody should file a PR, though.

Richard.

Follow-Ups:
- Re: A gcc-cris bug?
  - From: Andrew Pinski

References:
- RE: A gcc-cris bug?
  - From: Diego Novillo
- RE: A gcc-cris bug?
  - From: Dave Korn

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]