public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul de Vrieze" <pauldv@gentoo.org>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] [ANN] CFLAGS Builder
Date: Mon, 19 May 2003 13:13:24 +0200 (CEST)	[thread overview]
Message-ID: <62622.134.188.150.80.1053342804.squirrel@callisto.cs.kun.nl> (raw)



David Nielsen said:
> The -mcpu flag is depricated in GCC 3.3 - and should not be used
anymore. So in all fairness it would be best not to record it's usage,
it might mislead some users.

The only depreciation I could find concerning mcpu is in the mips port,
where it might not me appropriate. For x86 architectures it is available
though and it also serves a needed option as it determines instruction
scheduling. The march option does not, the march option determines which
instructions are used. As scheduling for an architecture lower than the
instructions is pointless implying mcpu makes sense. It is perfectly legal
though to specify
CFLAGS="-march=pentium -mcpu=pentium4" This would create code that runs on
anything bigger than a pentium, but is optimally scheduled for the
pentium4 processor. Scheduling has become increasingly important with the
newer (pentium and further) processors as they have the ability to run
some (but not all) instructions paralel to eachother. A p4 though provides
more pipelines than a p1, so instructions need to be scheduled differently
to optimally use all pipelines.

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net


-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net




--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-05-19 11:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-19 11:13 Paul de Vrieze [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-18  6:21 [gentoo-dev] [ANN] CFLAGS Builder Robin H.Johnson
2003-05-18 16:16 ` Alec Berryman
2003-05-18 23:18   ` Kevin Hayes
2003-05-19  8:13     ` Paul de Vrieze
2003-05-19 10:25       ` David Nielsen

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=62622.134.188.150.80.1053342804.squirrel@callisto.cs.kun.nl \
    --to=pauldv@gentoo.org \
    --cc=gentoo-dev@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