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: Andrew Pinski <pinskia at physics dot uc dot edu>, Richard Guenther <richard dot guenther at gmail dot com>, gcc at gcc dot gnu dot org, Dave Korn <dk at artimi dot com>, Diego Novillo <dnovillo at redhat dot com>, Tal Agmon <tal dot agmon at nsc dot com>
Date: Wed, 6 Oct 2004 15:56:34 +0200
Subject: Re: A gcc-cris bug?
References: <1097064169.26172.25.camel@localhost.localdomain> <NUTMEGG14dvQO3I9EOl000002b3@NUTMEG.CAM.ARTIMI.COM> <84fc9c0004100605482264aac@mail.gmail.com> <F3EDEA36-1796-11D9-B1A5-000A95D692F4@physics.uc.edu> <20041006134749.GA22707@nevyn.them.org>
Reply-to: Richard Guenther <richard dot guenther at gmail dot com>

> But, thanks to our abject lack of unit testing, there is no way to see
> if the problem still exists in 4.0.0.  Experience suggests that it
> does, and will need a much more complicated testcase (to get through
> the tree optimizers to whatever RTL optimizer is buggy).

One way of doing this is to analyze and fix the problem for 3.4 and
then possibly forward-port the fix.  But it ain't a regression...

Richard.

Follow-Ups:
- RE: A gcc-cris bug?
  - From: Dave Korn

References:
- RE: A gcc-cris bug?
  - From: Diego Novillo
- RE: A gcc-cris bug?
  - From: Dave Korn
- Re: A gcc-cris bug?
  - From: Richard Guenther
- Re: A gcc-cris bug?
  - From: Andrew Pinski
- Re: A gcc-cris bug?
  - From: Daniel Jacobowitz

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