public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
To: ivan@yosifov.net, Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Noob question. Why is the for-pentium4 kernel built with 	-march=i686 ?
Date: Tue, 19 Jul 2005 22:12:24 +0200	[thread overview]
Message-ID: <E1DuyS0-00013Z-VG@be1.lrz> (raw)
In-Reply-To: 4s5aD-1sw-3@gated-at.bofh.it

Ivan Yosifov <ivan@yosifov.net> wrote:

> -march implies -mtune and also implies thing like -msse2 for the
> instruction set where applicable.
> I think -march=pentium4 is equivalent to -mmmx -msse -msse2
> -mtune=pentium4 ( if I have not fogotten anything ).
> Pentium4 supports things like sse2 and mmx which AFAIK plain i686 does
> not.

AFAIK it's not possible to use SSE and MME in kernel mode, since these
registers aren't preserved (it would be expensive).
-- 
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

       reply	other threads:[~2005-07-19 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4s3M3-ph-15@gated-at.bofh.it>
     [not found] ` <4s4y2-Rt-17@gated-at.bofh.it>
     [not found]   ` <4s5aD-1sw-3@gated-at.bofh.it>
2005-07-19 20:12     ` Bodo Eggert [this message]
2005-07-19 20:15       ` Noob question. Why is the for-pentium4 kernel built with -march=i686 ? Jan Engelhardt
2005-07-19 20:19         ` Lee Revell
2005-07-19 17:07 Ivan Yosifov
2005-07-19 17:52 ` Jan Engelhardt
2005-07-19 18:35   ` Ivan Yosifov
2005-07-20  8:03     ` Kerin Millar
2005-07-20  7:57       ` Jan Engelhardt
2005-07-20  8:23       ` Ivan Yosifov
2005-07-20  9:21         ` Jan Engelhardt
2005-07-20  9:44         ` Kerin Millar
2005-07-20  9:25           ` Ivan Yosifov
2005-07-20 10:38             ` Denis Vlasenko
2005-07-20 11:33               ` Ivan Yosifov
2005-07-20 11:42               ` Simon Strandman
2005-07-20 14:29                 ` Dave Neuer

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=E1DuyS0-00013Z-VG@be1.lrz \
    --to=harvested.in.lkml@posting.7eggert.dyndns.org \
    --cc=7eggert@gmx.de \
    --cc=ivan@yosifov.net \
    --cc=jengelh@linux01.gwdg.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox