All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Gurdasani <amitg@alumni.cmu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: Pentium M config option for 2.6
Date: Mon, 5 Jan 2004 19:09:58 +0400 (GST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0401051858540.4783@athena.localdomain> (raw)

:On Date: Sun, 4 Jan 2004 13:33:58 +0100, Tomas Szepe wrote:
:> > IOW, don't lie to the compiler and pretend P-M == P4
:> > with that -march=pentium4.
:>
:> What do you recommend to use as march then?  There is
:> no pentiumm subarch support in gcc yet;  I was convinced
:> p4 was the closest match.
:
:march=pentium3 is the closest safe choice, at least
:until gcc implements P-M specific support.
:
:/Mikael

Perhaps -mcpu=pentium3 -march=pentium4 would be a good compromise? From the
GCC 3.3 info pages:

`-mcpu=CPU-TYPE'
     Tune to CPU-TYPE everything applicable about the generated code,
     except for the ABI and the set of available instructions. [...]

     While picking a specific CPU-TYPE will schedule things
     appropriately for that particular chip, the compiler will not
     generate any code that does not run on the i386 without the
     `-march=CPU-TYPE' option being used. [...]

`-march=CPU-TYPE'
     Generate instructions for the machine type CPU-TYPE.  The choices
     for CPU-TYPE are the same as for `-mcpu'.  Moreover, specifying
     `-march=CPU-TYPE' implies `-mcpu=CPU-TYPE'.

Amit

             reply	other threads:[~2004-01-05 15:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-05 15:09 Amit Gurdasani [this message]
2004-01-05 15:22 ` Pentium M config option for 2.6 Tim Schmielau
  -- strict thread matches above, loose matches on Subject: below --
2004-03-29 15:42 Mikael Pettersson
2004-03-29 15:42 Mikael Pettersson
2004-01-04 14:10 Mikael Pettersson
2004-01-04 14:43 ` Tomas Szepe
2004-01-04 15:59   ` Ciaran McCreesh
2004-03-29 15:42   ` Ciaran McCreesh
2004-03-29 15:42 ` Tomas Szepe
2004-01-04 12:27 Mikael Pettersson
2004-01-04 12:33 ` Tomas Szepe
2004-01-06  6:07   ` Jakob Oestergaard
2004-03-29 15:46   ` Jakob Oestergaard
2004-01-04 15:03 ` Rob Love
2004-01-04 16:25   ` Dave Jones
2004-01-04 16:33     ` Rob Love
2004-01-04 16:50       ` Dave Jones
2004-01-04 17:01         ` Rob Love
2004-01-04 17:14           ` Tomas Szepe
2004-03-29 15:42           ` Tomas Szepe
2004-01-04 17:03         ` Troels Walsted Hansen
2004-01-04 17:35           ` Dave Jones
2004-01-04 21:51         ` Vojtech Pavlik
2004-03-29 15:42         ` Rob Love
2004-01-04 20:34       ` Valdis.Kletnieks
2004-01-04 21:55         ` Vojtech Pavlik
2004-01-04 23:37           ` Valdis.Kletnieks
2004-03-29 15:42       ` Dave Jones
2004-03-29 15:42     ` Rob Love
2004-03-29 15:42   ` Dave Jones
2004-03-29 15:42 ` Tomas Szepe
2004-03-29 15:42 ` Rob Love
2004-01-04  2:28 Tomas Szepe

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=Pine.LNX.4.56.0401051858540.4783@athena.localdomain \
    --to=amitg@alumni.cmu.edu \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.