On 2002-06-21 16:35 +0200, Martin Blapp <[EMAIL PROTECTED]> wrote:
> I still wonder why we make workarounds like this if one could just
> use /usr/local/bin/gcc31 to have it fixed.

Sorry, but the compiler bug has been present in the port version
of GCC-3.1 as well, a few weeks ago, and existed in the version
to become GCC-3.1.1 ...

I opened a PR at gcc.org, didn't get any feedback, yet.

> Why mess around with a buggy compiler if a working one is around ?

Only a single source file triggers the optimizer bug, and the
work-around should be appropriate until the compiler is fixed,

> Why don't we update the pre 3.1 gcc in CURRENT to a working one ?

I'm sure that there is a lot of work being done to keep up with
the latest gcc versions. It just isn't that simple to upgrade such
a crucial build tool (if compiling a new gcc fails, then make world
doesn't have much of a chance of succeeding ...)

> Yes, I turned on -O and O2 again ;-)

Did the GCC-3.1 from ports compile translate.c with optimization
turned on ???

It didn't, just one or two weeks ago.

Regards, STefan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to