Alexander Leidinger wrote:
>The GCC developers usually want to have a short example whit the
>breakage, so the submitter has at least to find the file which needs to
>be compiled with "-O3 -funroll-loops" to reveal the bug. Better would be
>to compare the output after the assembly stage and to construct a small
>example which reproduces the bug.
>
I've been trying to do this for about a week now (when I've had extra
time, that is). It is
frustratingly difficult to pinpoint the location where things start to
go wrong (in order to be
able to write a small test case for gcc developers). However, I'm slowly
making progress.
It is quite possible that this bug has already been found and fixed. I
tried to compile lame
with a recent experimental version of gcc 3.1 (which should be ready on
April), and it
didn't give any errors.
Anyway, the release notes of 3.0.3 say that the release was mainly made
to make gcc work
on some platforms where it didn't work previously, so I've decided to
continue using 3.0.2 until
3.1 is ready.
--
------------ Matti Rintala -------- [EMAIL PROTECTED] ---------
"When the remarkable turns bizarre, reason turns rancid."
Cheshire Cat in "American McGee's Alice"
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
