All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Nick Lowe <nick.lowe@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promoting Crusoe and Geode Processors to i686 Status
Date: Wed, 08 Sep 2010 15:15:46 -0700	[thread overview]
Message-ID: <4C880B12.3040200@zytor.com> (raw)
In-Reply-To: <AANLkTimp5kh3Wg5kzfCWq0Rz3uCL7ivu+TED1oHcFDP8@mail.gmail.com>

On 09/08/2010 03:14 PM, Nick Lowe wrote:
> Hi,
> 
> Here goes...
> 
> -mtune tunes the binary for given architecture. This as opposed to
> defining the baseline architecture, and thus available instruction
> set, which -march does.
> 
> I believe that -mtune is predominantly used for instruction
> scheduling. GCC uses it when it's reordering instructions to optimise
> for specific micro-architecture over others.
> 
> With -mtune=i686, I am of the opinion that you instruct the compiler,
> and give it the opportunity, to deliver a better ordering of the
> instructions. In this case, better ordering for i686 than you would
> get with -mtune=generic32.
> 
> I'm probably wrong somehow, it's probably marginal, and I'll concede
> to your infinitely better knowledge any day! That's why I phrased it
> as a question! :)
> 

We don't pass -mtune=generic32 to gcc.  We pass -Wa,-mtune=generic32 to
gcc, which affects binutils only.

	-hpa

      reply	other threads:[~2010-09-08 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 22:12 Promoting Crusoe and Geode Processors to i686 Status Nick Lowe
2010-09-08  0:27 ` Nick Lowe
2010-09-08 21:39   ` H. Peter Anvin
2010-09-08 22:14     ` Nick Lowe
2010-09-08 22:15       ` H. Peter Anvin [this message]

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=4C880B12.3040200@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick.lowe@gmail.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.