From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] New computer and Gentoo
Date: Thu, 21 Jul 2011 15:57:13 +0700 [thread overview]
Message-ID: <jGNsKwmprbmY.p3gJYCqF@smtp.gmail.com> (raw)
-original message-
Subject: Re: [gentoo-user] New computer and Gentoo
From: Bill Kenworthy <billk@iinet.net.au>
Date: 2011-07-21 12:54
>On Thu, 2011-07-21 at 06:26 +0100, Mick wrote:
>> On Thursday 21 Jul 2011 03:29:17 Adam Carter wrote:
>> > amd64 means any x86 64bit platform, so Intel too.
>> >
>> > march=native is good if you're not using distcc, or if you're only
>> > using distcc on core2 boxes. Otherwise be specific.
>>
>> I recommend using the "64 bit profile (amd64) for >= GCC 4.3" which shows -
>> march=core2. This is what I use here with multilib and had no problems.
>
>Ive just stumbled on something weird with march=native:
>
>At some point I had march=prescott on a core2 E4600 running 32bit -
>worked well. Changed to march=native and did some upgrades with a few
>odd things like asterisk segfaulting in a glibc library afterwards, and
>some things not building. Then to add confusion, I changed to an
>pentium Duo E6600 (flies!) and added another stick of ram. More odd
>things happening such as reiserfs oopsing on shutdown.
>
>Last night the penny dropped and I looked the new processor up and
>changed to march=core2 and have mostly corrected (recompiled) the
>damage.
>
>So not sure about march=native now as it is only what was built with
>native thats been problematic. With 20-20 hindsight it was perhaps
>predictable ...
IMO you're not supposed to compile part of the system with -march=<something> and the rest with -march=native. The instructions (and optimizations) emitted by -march=native might not be compatible with your previous -march.
I had deployed more than 10 Gentoo servers using -march=native without any problem.
CMIIW
Rgds,
--
FdS Pandu E Poluan
~ IT Optimizer ~
Sent from Nokia E72-1
next reply other threads:[~2011-07-21 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 8:57 Pandu Poluan [this message]
2011-07-21 9:21 ` [gentoo-user] New computer and Gentoo Florian Philipp
2011-07-21 9:52 ` Pandu Poluan
2011-07-21 9:56 ` Florian Philipp
2011-07-21 13:10 ` William Kenworthy
2011-07-21 14:05 ` Florian Philipp
2011-07-23 13:40 ` Stroller
-- strict thread matches above, loose matches on Subject: below --
2011-07-21 2:23 CJoeB
2011-07-21 2:29 ` Adam Carter
2011-07-21 5:26 ` Mick
2011-07-21 5:54 ` Bill Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jGNsKwmprbmY.p3gJYCqF@smtp.gmail.com \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox