From: "Jakob Oestergaard" <jakob@unthought.net>
To: <Administrator@smtp.paston.co.uk>
Cc: "Mikael Pettersson" <mikpe@csd.uu.se>, <akpm@osdl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: Pentium M config option for 2.6
Date: Mon, 29 Mar 2004 16:46:26 +0100 [thread overview]
Message-ID: <049201c415a4$feebc2a0$d100000a@sbs2003.local> (raw)
In-Reply-To: <20040104123358.GB24913@louise.pinerecords.com>
On Sun, Jan 04, 2004 at 01:33:58PM +0100, Tomas Szepe wrote:
> On Jan-04 2004, Sun, 13:27 +0100
> Mikael Pettersson <mikpe@csd.uu.se> 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.
Use the same as for P-III.
The P-M has the same instruction decoder (and execution unit) setup as
the P-III, which is *very* different from P-IV (which has one decoder
only, and then a trace cache for the decoded uops). This is an
important difference from a code generator point of view.
>From reading Intel's optimization guides, it seems to me like the P-M is
pretty much just a slightly enhanced P-III (more cache AFAIR) which
happens to get shipped with a good mobile chipset - and that package
together is called Centrino.
That would also explain why Centrino leaves the P-IV based laptops in
the dust ;)
Cheers,
/ jakob
next prev parent reply other threads:[~2004-03-29 15:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 12:27 Pentium M config option for 2.6 Mikael Pettersson
2004-01-04 12:33 ` Tomas Szepe
2004-01-06 6:07 ` Jakob Oestergaard
2004-03-29 15:46 ` Jakob Oestergaard [this message]
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
-- 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-05 15:09 Amit Gurdasani
2004-01-05 15:22 ` Tim Schmielau
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 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='049201c415a4$feebc2a0$d100000a@sbs2003.local' \
--to=jakob@unthought.net \
--cc=Administrator@smtp.paston.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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