This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: sparc-sun-solaris2.6 egcs-1.1.2 post increment bug
- To: Mike Stump <mrs at wrs dot com>
- Subject: Re: sparc-sun-solaris2.6 egcs-1.1.2 post increment bug
- From: Brian Ford <ford at vss dot fsi dot com>
- Date: Tue, 27 Jul 1999 09:00:30 -0500 (CDT)
- cc: gcc-bugs at gcc dot gnu dot org
On Thu, 22 Jul 1999, Mike Stump wrote:
> > Date: Thu, 22 Jul 1999 14:20:26 -0500 (CDT)
> > From: Brian Ford <ford@vss.fsi.com>
>
> > I verified that this is fixed in gcc-2.95, but I can't believe a bug
> > this big got out the door for egcs-1.1.2 on sparc-sun-solaris2.6. I
> > follow the list pretty closely, and I haven't seen mention of this.
> > I guess I may have missed it though. This makes egcs-1.1.2 very
> > buggy on this platform. Shouldn't we post a warning about this
> > somewhere?
>
> No. A note to one of the bug lists is enough. If it were serious
> enough, we would have had a 1.1.3 release that fixed it, since we
> didn't, we can conclude that it really wasn't as big as you make it
> out to be. I know how bad that sounds from your perspective, I mean,
> any bug in a release is wrong, but then reality sets in. The truth it
> that we ship with lots of know bugs, any as the potential to make life
> really hard for an individual. Part of our job is to identify the
> ones that must be fixed, and fix them and to ensure that the general
> quality of the compiler remains high.
>
Ok. I understand no warning needs to be posted, especially in light of
the eminent gcc-2.95 release that fixes the bug. I think a silent codegen
bug for something as simple as pre and post increment *is* pretty big.
But, I didn't mean to sound as if I was that *bothered* by it.
I think egcs, now gcc, is a very good compiler and I applaud all the
volunteer effort that is put in. I hope, though, that there is a test
case in the testsuite for something as basic as this. It seems like an
embarrasing bug to let out the door. I hope it was not known at release
time, or if it was, I hope it was going to be a bear to fix.
Thank you for the reply.
--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax: 314-551-8444