From: Gabriel C <nix.or.die@googlemail.com>
To: Michael Lothian <mike@fireburn.co.uk>
Cc: Adrian Bunk <bunk@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: Possibility of adding -march=native to x86
Date: Thu, 25 Oct 2007 22:40:11 +0200 [thread overview]
Message-ID: <4720FF2B.9020802@googlemail.com> (raw)
In-Reply-To: <fc94aae90710251312w2eba46e8h5d4f8715ad0e91b6@mail.gmail.com>
Michael Lothian wrote:
>> The MPENTIUM4 option does not only set -march=pentium4, it also enables
>> several other options in arch/i386/Kconfig.cpu resulting in better
>> performance.
>
> How about an autodetect to set the right options here too using cpuid?
>
> With a warning of course that the code produced will be specifically
> for the native cpu that it's compiled on.
And kill off all Distro kernels right ? IMO to set that auto magically is bad.
Regards,
Gabriel
next prev parent reply other threads:[~2007-10-25 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0EC33A59AA72084CA28B83816B40929F02682BB3@REEDXCLSXM01V03.rbsres01.net>
2007-10-25 18:33 ` Possibility of adding -march=native to x86 Michael Lothian
2007-10-25 18:50 ` Adrian Bunk
2007-10-25 19:09 ` Michael Lothian
2007-10-25 19:17 ` Adrian Bunk
2007-10-25 19:32 ` Michael Lothian
2007-10-25 19:50 ` Adrian Bunk
2007-10-25 20:12 ` Michael Lothian
2007-10-25 20:20 ` Adrian Bunk
2007-10-25 20:20 ` Arjan van de Ven
2007-10-26 10:41 ` Pádraig Brady
2007-10-26 11:45 ` Adrian Bunk
2007-10-25 20:40 ` Gabriel C [this message]
2007-10-25 21:30 ` Michael Lothian
2007-10-25 21:46 ` Adrian Bunk
2007-10-25 22:04 ` H. Peter Anvin
2007-10-25 22:42 ` Michael Lothian
2007-10-25 22:58 ` Adrian Bunk
[not found] ` <fc94aae90710251518l1cc129eahf570177e5b516197@mail.gmail.com>
[not found] ` <20071025222826.GY30533@stusta.de>
2007-10-25 22:58 ` Michael Lothian
2007-10-26 9:16 ` Thomas Gleixner
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=4720FF2B.9020802@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@fireburn.co.uk \
/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