All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Neuer <mr.fred.smoothie@gmail.com>
To: Simon Strandman <simon.strandman@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Noob question. Why is the for-pentium4 kernel built with -march=i686 ?
Date: Wed, 20 Jul 2005 10:29:52 -0400	[thread overview]
Message-ID: <161717d505072007293830074a@mail.gmail.com> (raw)
In-Reply-To: <42DE3890.2040501@telia.com>

On 7/20/05, Simon Strandman <simon.strandman@telia.com> wrote:
> Denis Vlasenko skrev:
> 
> >
> >Why do you care? I bet that differences between i686 code and pentium4 code
> >are well below noise level.
> >--
> >vda
> >
> For x86_64 the flags -mno-sse -mno-mmx -mno-sse2 -mno-3dnow are always
> used for compilation. Why is'nt the same thing done for x86 instead of
> using -march=i686 -mtune=?.
> 
> -march=athlon and -march=k6 includes -m3dnow and -mmmx, are those ok for
> the kernel but -msse isn't?
> 

As Kerin pointed out, gcc 4.0 supports auto-vectorization, so in
theory, these options might provide better performance on some
compilers. Apparently SSE is not enabled by default any more for P4
because of a known bug w/ some compilers. People using gcc > 4.0 can
obviously override it.

Really, w/out the presence of auto-vectorization support in the
compiler none of the vector extensions are necessary. The only things
that really matter are -mcpu and -mtune: what instruction set your CPU
supports and the optimum instruction scheduling characteristics for
your CPU, respectively.

Dave

  reply	other threads:[~2005-07-20 14:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 17:07 Noob question. Why is the for-pentium4 kernel built with -march=i686 ? 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 [this message]
     [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
2005-07-19 20:15       ` Jan Engelhardt
2005-07-19 20:19         ` Lee Revell

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=161717d505072007293830074a@mail.gmail.com \
    --to=mr.fred.smoothie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mr.fred.smoothie@pobox.com \
    --cc=simon.strandman@telia.com \
    /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.