1 |
On Sat, Jun 2, 2012 at 11:56 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov |
3 |
> <dgoncharov@××××××××.net> wrote: |
4 |
>> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote: |
5 |
>>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol <mikemol@×××××.com> wrote: |
6 |
>>> Wow. Just wow. This is incredible. |
7 |
>>> |
8 |
>>> This is repeatable for me. |
9 |
>>> |
10 |
>> <snip> |
11 |
>>> * The problem occurred while executing the ebuild file named |
12 |
>>> * 'glibc-2.14.1-r3.ebuild' located in the '/var/db/pkg/sys- |
13 |
>>> |
14 |
>> <snip> |
15 |
>>> CFLAGS="-O2 -pipe -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf |
16 |
>>> --param l1-cache-size=32 --param l1-cache-line-size=64 --param |
17 |
>>> l2-cache-size=4096 -mtune=core2 -ggdb3" |
18 |
>>> CXXFLAGS="${CFLAGS}" |
19 |
>> |
20 |
>> Can you upgrage to glibc-2.15? |
21 |
> |
22 |
> Sure. It's going to be another full reinstall. |
23 |
|
24 |
Forgot to try this. Will do tomorrow. |
25 |
|
26 |
> |
27 |
>> Can you tweak you gcc flags to something more conventional and see if the |
28 |
>> problem persists? |
29 |
> |
30 |
> Those CFLAGS should be equivalent to: |
31 |
> CFLAGS="-O2 -pipe -ggdb3 --march=native". |
32 |
> |
33 |
> But I'll try making it just -O2 -pipe --march=native. |
34 |
|
35 |
Just an update: Tried CFLAGS="-O2 -pipe --march=native -ggdb3". Same results. |
36 |
|
37 |
> |
38 |
>> If you are interested in submitting a patch to the upstream then you can build |
39 |
>> the glibc test suite with your gcc flags and check if the tests pass. |
40 |
|
41 |
I do still have a working gentoo laptop I could try this on...but it |
42 |
has an i3 proc, as opposed to the core 2 xeon or the phenom 9650. Have |
43 |
a link to instructions? |
44 |
|
45 |
-- |
46 |
:wq |