------- Comment #6 from mikael at gcc dot gnu dot org 2008-12-15 00:14 -------
(In reply to comment #4)
> Sounds a bit like the problem from comment #0 is a duplicate or related to
> PR31537 and/or PR35034 ?
>
31537 seems definitely related.
Is there a specific option/configuration to reproduce/bypass it?
(In reply to comment #5)
> Responding to comment #3: *Ahem*. I tried with today's live sources
> (revision 142751). I got as far as building libgfortran in stage 3, and
> *bang*. Bug 35828, which see. It's not obviously related to the
> problem here (though presumably there are some options which don't
> produce it, of which --enable-intermodule may perhaps be one).
>
s/Bug 35828/Bug 38528/
It seems some configure options are not much tested. :-(
Something has just come to my mind.
Since you are on i686-pc-linux-gnu, I'm not sure it is legal to specify
-march=athlon64-sse3 as it will use the 64 bits extensions.
>From the gcc manual:
_k8, opteron, athlon64, athlon-fx_
AMD K8 core based CPUs with x86-64 instruction set support.
(This supersets MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW! and
64-bit instruction set extensions.)
_k8-sse3, opteron-sse3, athlon64-sse3_
Improved versions of k8, opteron and athlon64 with SSE3
instruction set support.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37865
