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: Simple code produces ICE in gcc-3.2.1


On Thu, Oct 24, 2002 at 08:11:09AM +0200, Andreas Jaeger wrote:
> Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
> 
> > On Wed, Oct 23, 2002 at 10:15:22PM -0700, Andrew Pinski wrote:
> >> This also happens on a i686-pc-linux-gnu gcc 3.3,
> >> but does not happen on a i686-pc-linux-gnu gcc 3.1.1
> >> so it is a regression report it to the bug system, please.
> >> 
> >> 3.3's version:
> >> gcc version 3.3 20021023 (experimental)
> >> 
> >> 
> >
> > I did.  I sent email to gcc-bugs@gcc.gnu.org
> 
> Did you file it with gnats to our bug database?  An email sent to
> gcc-bugs will be lost, it really needs to be in the database.  Use
> gccbug or the web interface to gnats to file the report,
> 

Man, the gnatsweb interface real sucks.  After 6 hours
of reducing a rather complex chuck of code to 10 lines.
I had to try 4 times to get a report filed.

Why offer a priority field of "high" if it can't be
set?  Why have a submitter-id field when only a 
single choice is validate?  Why ask for the release
info when you also ask for the output of gcc -v?

Look for a PR with the same subject line.  The
GNATS system hasn't registered my PR, yet.

-- 
Steve


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