public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CFLAGS for both AMD64 and Intel?
Date: Sun, 3 Dec 2017 02:40:07 -0500	[thread overview]
Message-ID: <CAJ0EP42CXzaoVWG50J+An_YrxJMaN6fjiaZ62dLhW71VdV0RAQ@mail.gmail.com> (raw)
In-Reply-To: <CAGJrxsS5qkio1vi3CQj81AuX9VKWQrr9hzrSX7=U+KJM-7WobA@mail.gmail.com>

On Sun, Dec 3, 2017 at 2:23 AM, Manuel McLure <manuel@mclure.org> wrote:
> Here's the situation. I have a system that's been running for many years
> with an Athlon 5050e processor. The system is built with
>
> CFLAGS="-march=k8-sse3 -O2 -pipe -msse3"
> CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3"
>
> I have the possibility of upgrading the system to a first-generation Intel
> Core i5 which should give a nice speed boost, but of course the Intel chip
> doesn't understand 3dnow or 3dnowext, so I'll have to do a system rebuild
> before I switch out the motherboard/processor. It seems pretty obvious that
> I have to take "3dnow 3dnowext" out of CPU_FLAGS_X86, but what CFLAGS would
> be recommended for a system that will still run with the AMD processor but
> won't fall over when I switch to the Intel processor? Once I have the Intel
> in place I can rebuild with options more suited for that chip, but I want to
> make sure I don't end up in a catch-22 situation.

I would go with just "-O2 -pipe" for maximum compatibility. Remove the
-march option altogether, and add it back once the system is running
on the Intel chip.


  reply	other threads:[~2017-12-03  7:40 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 [this message]
2017-12-03  8:08 ` Walter Dnes
2017-12-05 19:09   ` Manuel McLure

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=CAJ0EP42CXzaoVWG50J+An_YrxJMaN6fjiaZ62dLhW71VdV0RAQ@mail.gmail.com \
    --to=floppym@gentoo.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