public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: GCC-4.3.2
Date: Mon, 6 Apr 2009 10:35:56 -0600	[thread overview]
Message-ID: <20090406163556.GI6904@syscon4.inet> (raw)
In-Reply-To: <grcg4h$14m$1@ger.gmane.org>

On 04/06/09 11:56, Nikos Chantziaras wrote:

[snip]
>>> ~adj~
>> I just notice that there is a problem with CFLAGS -march=native on AMD64
>> I recompile my system using this new flag and have a lot of problems. an 
>> examples new xorg-server-1.5... would not compile, I switch back to my 
>> previous settings:
>> -march=athlon64 and it compiled on first pass.
>> So, now I'm recompiling the system with my old flag: -march=athlon64 :-/
>
> -march=native is only useful if you don't know what to use.  I guess most 
> Gentoo users do know what to use.  Why should I use "native" if I know that 
> my CPU is "athlon64" :P

Well, according to gentoo recommendations it is not so:
http://en.gentoo-wiki.com/wiki/Safe_Cflags
"...GCC 4.2 introduces a new -march option, -march=native, which automatically detects the features your CPU supports and sets the options appropriately. 
If you have an Intel or AMD CPU and are using >=sys-devel/gcc-4.2.3, using -march=native is recommended...."

So, I suggest you make a correction to gentoo-wiki, as I suspect I'll will not be the only one who get confused by it :-/

-- 
Joseph



  reply	other threads:[~2009-04-06 16:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  8:34 [gentoo-user] GCC-4.3.2 alain.didierjean
2009-04-03 10:24 ` Thomas Kahle
2009-04-03 12:17 ` Masood Ahmed
2009-04-03 21:15   ` Neil Bothwick
2009-04-03 21:28     ` Jerry McBride
2009-04-04  5:43   ` Mike Kazantsev
2009-04-04  8:28     ` Graham Murray
2009-04-03 14:53 ` alain.didierjean
2009-04-04  7:03 ` Christopher Walters
2009-04-06  6:02 ` Joseph
2009-04-06  8:56   ` [gentoo-user] GCC-4.3.2 Nikos Chantziaras
2009-04-06 16:35     ` Joseph [this message]
2009-04-06 20:07       ` Neil Bothwick
2009-04-06 20:28         ` Joseph
2009-04-06 20:37           ` Paul Hartman
2009-04-06 22:20           ` Neil Bothwick
2009-04-06 16:53     ` Jarry
2009-04-06 17:52       ` Joseph
2009-04-07  2:53       ` Nikos Chantziaras
2009-04-07  1:00   ` [gentoo-user] GCC-4.3.2 Jorge Morais
2009-04-07  2:19     ` Joseph
2009-04-07 14:42       ` Mike Kazantsev
2009-04-07 16:48       ` Arttu V.
2009-04-07 18:07         ` Joseph

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=20090406163556.GI6904@syscon4.inet \
    --to=syscon780@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