On Sat, Jun 02, 2012 at 11:56:01PM -0400, Michael Mol wrote:
> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
> <dgoncha...@users.sf.net> wrote:
> > On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
> >> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol <mike...@gmail.com> wrote:
> >> Wow. Just wow. This is incredible.
> >>
> >> This is repeatable for me.
> >>
> > <snip>
> >> * The problem occurred while executing the ebuild file named
> >> * 'glibc-2.14.1-r3.ebuild' located in the '/var/db/pkg/sys-
> >>
> > <snip>
> >> CFLAGS="-O2 -pipe -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf
> >> --param l1-cache-size=32 --param l1-cache-line-size=64 --param
> >> l2-cache-size=4096 -mtune=core2 -ggdb3"
> >> CXXFLAGS="${CFLAGS}"
> >
> > Can you upgrage to glibc-2.15?
>
> Sure. It's going to be another full reinstall.
>
> > Can you tweak you gcc flags to something more conventional and see if the
> > problem persists?
>
> Those CFLAGS should be equivalent to:
> CFLAGS="-O2 -pipe -ggdb3 --march=native".
>
> But I'll try making it just -O2 -pipe --march=native.
>
> > If you are interested in submitting a patch to the upstream then you can
> > build
> > the glibc test suite with your gcc flags and check if the tests pass.
>
> If it gets things fixed. I have two machines which have been offline
> for almost two months from this.
>
> --
> :wq
>
Also, which gcc are you using? Can you try a different version?
regards, Dmitry
