From: Denis <denis.che@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf?
Date: Thu, 24 May 2007 11:13:30 -0400 [thread overview]
Message-ID: <d9a0a6da0705240813j3e2121sf112e31f37437ceb@mail.gmail.com> (raw)
In-Reply-To: <642958cc0705240717s360e212er3f54e8636e5a06f1@mail.gmail.com>
After reading some docs, the impression I get is that the 'nocona'
flag is for building a 64-bit system... For a 32-bit system, it seems
like 'prescott' would be the choice, wouldn't it?
This from the GCC website about 4.2.0 release changes:
IA-32/x86-64
* -mtune=generic can now be used to generate code running well on
common x86 chips. This includes AMD Athlon, AMD Opteron, Intel
Pentium-M, Intel Pentium 4 and Intel Core 2.
* -mtune=native and -march=native will produce code optimized for
the host architecture as detected using the cpuid instruction.
* Added a new command line option -fstackrealign and and
__attribute__ ((force_align_arg_pointer)) to realign the stack at
runtime. This allows functions compiled with a vector-aligned stack to
be invoked from legacy objects that keep only word-alignment.
We don't have gcc-4.2.0 in our portage available for installation yet,
do we? Anyone know when?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-24 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 13:55 [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf? Denis
2007-05-24 14:15 ` Ryan Sims
2007-05-24 14:17 ` Mark Shields
2007-05-24 15:13 ` Denis [this message]
2007-05-24 15:43 ` Neil Bothwick
2007-05-24 15:55 ` Graham Murray
2007-05-24 16:38 ` Denis
2007-05-25 7:22 ` Randy Barlow
2007-05-24 15:30 ` [gentoo-user] " Alexander Skwar
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 9:10 [gentoo-user] " burlingk
2007-05-25 17:03 ` Andreas Claesson
2007-05-25 18:26 ` Denis
2007-05-28 3:05 ` Randy Barlow
2007-05-31 1:11 ` Dan Farrell
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=d9a0a6da0705240813j3e2121sf112e31f37437ceb@mail.gmail.com \
--to=denis.che@gmail.com \
--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