On Thu, 2011-07-21 at 11:21 +0200, Florian Philipp wrote:
> Am 21.07.2011 10:57, schrieb Pandu Poluan:
> > -original message-
> > Subject: Re: [gentoo-user] New computer and Gentoo
> > From: Bill Kenworthy <bi...@iinet.net.au>
> > Date: 2011-07-21 12:54
> > 
> >> On Thu, 2011-07-21 at 06:26 +0100, Mick wrote:
> [...]
> >> Ive just stumbled on something weird with march=native:
> >>

> 
> I'd like to see a reference for this claim. -march=native doesn't do
> more than set -march=core2 and some other optimizations for cache size
> etc. This should be no more troublesome than mixing code compiled with

unfortunately this is now my main machine so I cant fiddle too much with
it!  It would mean going back to the E4600 and comparing march=prescott,
march=native then fitting the E6600 and checking march=native and
march=core2.  What I cant find is a reference to how it works out what
native is? - lookup-table, checking the flags in /proc/cpuinfo or what?

Ive now rolled back (that is recompiled) the majority of packages so now
I can keep working while it does an emerge -e world.

I would have thought the two intel processors would be close enough that
it would be just a performance hit and not segfaults, but the machine is
now working reliably so thats proof enough for me.  What I am having
difficulty with is that packages compiled with native should have been a
closer match to the cpu so why was it those packages (asterisk, glibc
and some random others cause problems.

BillK




Reply via email to