Date:	Sat, 11 Dec 93 21:41:00 -0500
From:	DJ Delorie <dj AT ctron DOT com>
To:	peprbv AT cfa0 DOT harvard DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: reporting bugs in gcc

> Where's the best place (newsgroup, mailing list, etc.) to report an apparent
> code generation bug?  (I know that DJ is not responsible for fixing this
> sort of thing.)  What I'm seeing is that, in a C routine with a variable
> number of arguments, ebx is being used to step through the list of arguments,
> but the inital ebx value is setup wrong.  I've recompiled the offending
> routine with 1.10, and it then works.  I've also looked at assembly language
> output, and the 1.11 code is clearly wrong.  Will the FSF be interested in
> this report, given that there have been (I think) two releases of gcc since
> the one used for 1.11?

What you should do is get the latest gcc (2.5.6 at the current time)
and rebuild cc1 to see if it is still a problem.  Even if you can't do
this, it's still worth reporting.

Bugs against gcc itself should be sent (preferrably) to gnu.gcc.bug or
bug-gcc AT prep DOT ai DOT mit DOT edu.  Please see the section in the gcc info files
about bug reports before reporting any.

- Raw text -