public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Manuel McLure <manuel@mclure.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CFLAGS for both AMD64 and Intel?
Date: Tue, 5 Dec 2017 11:09:35 -0800	[thread overview]
Message-ID: <CAGJrxsQvDboiy=wfe2rTSn3g9qqPM1m4TnSMZsQYWgme5dhMZQ@mail.gmail.com> (raw)
In-Reply-To: <20171203080852.GB30078@waltdnes.org>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Sun, Dec 3, 2017 at 12:08 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:

>
> https://gcc.gnu.org/onlinedocs/gcc-6.4.0/gcc/x86-Options.html#x86-Options
> lists what instruction sets gcc expects for any "-march=<whatever>"
>
>   I would suggest rebuilding with...
>
> CFLAGS="-march=nocona -O2 -pipe"
> CPU_FLAGS_X86="mmx sse sse2 sse3"
>
>   nocona was the first Intel cpu to support AMD64 instructions, and it's
> the newest Intel that does not exceed your AMD.  The next Intel cpu, the
> "core2" supports ssse3 which your AMD does not (count the "s"'s... very
> carefully; sse3 != ssse3).
>
>
Thanks! I have successfully rebuilt the system with "-march=nocona -O2
-pipe" (and switched to gcc 6.4.0/profile 17 while I was at it) and
everything seems to be running fine. Hopefully I can pick up a micro-ATX
LGA1156 motherboard for cheap and can do the processor upgrade soon.

-- 
Manuel A. McLure WW1FA <manuel@mclure.org> <http://www.mclure.org>
...for in Ulthar, according to an ancient and significant law,
no man may kill a cat.                       -- H.P. Lovecraft

[-- Attachment #2: Type: text/html, Size: 1945 bytes --]

      reply	other threads:[~2017-12-05 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03  7:23 [gentoo-user] CFLAGS for both AMD64 and Intel? Manuel McLure
2017-12-03  7:40 ` Mike Gilbert
2017-12-03  8:08 ` Walter Dnes
2017-12-05 19:09   ` Manuel McLure [this message]

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='CAGJrxsQvDboiy=wfe2rTSn3g9qqPM1m4TnSMZsQYWgme5dhMZQ@mail.gmail.com' \
    --to=manuel@mclure.org \
    --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