From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] -march=native is *EXTREMELY* conservative
Date: Sat, 17 Dec 2011 15:53:54 -0600 [thread overview]
Message-ID: <4EED0F72.5070605@gmail.com> (raw)
In-Reply-To: <20111217210709.GA1740@waltdnes.org>
Walter Dnes wrote:
> gcc -march=native -Q --help=target
If that shows something disabled that cat /proc/cpuinfo shows as
available, is it safe to turn it on? So far all I have found that is
disabled that cpuinfo shows is mmx. I'm still looking tho.
Also, I think the native setting is a setting that is known to be 100%
safe. It is likely one of those things that if you use anything not
safe and have problems, you get to keep the pieces. I think if the CPU
supports it should be fine to turn but wanted to ask and make sure. I
paid almost $200 for my CPU and I would like to get $200 out of it and
use it all. I bought the whole thing so may as well use the whole
thing. ;-)
Thoughts?
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Miss the compile output? Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"
next prev parent reply other threads:[~2011-12-17 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 21:07 [gentoo-user] -march=native is *EXTREMELY* conservative Walter Dnes
2011-12-17 21:53 ` Dale [this message]
2011-12-17 21:58 ` [gentoo-user] " Nikos Chantziaras
2011-12-18 1:10 ` Walter Dnes
2011-12-18 10:34 ` Walter Dnes
2011-12-18 10:45 ` Nikos Chantziaras
2011-12-18 18:10 ` Andrea Conti
2011-12-19 0:05 ` [gentoo-user] A tale of computing thud and blunder Walter Dnes
2011-12-19 0:17 ` Dale
2011-12-19 5:41 ` Pandu Poluan
2011-12-19 6:15 ` Dale
2011-12-19 6:49 ` [gentoo-user] " Nikos Chantziaras
2011-12-19 7:21 ` Dale
2011-12-19 12:49 ` walt
2011-12-19 8:14 ` [gentoo-user] " Pandu Poluan
2011-12-19 16:37 ` Paul Hartman
2011-12-18 1:15 ` [gentoo-user] -march=native is *EXTREMELY* conservative Paul Hartman
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=4EED0F72.5070605@gmail.com \
--to=rdalek1967@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