From: "Michael Lothian" <mike@fireburn.co.uk>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possibility of adding -march=native to x86
Date: Thu, 25 Oct 2007 20:09:56 +0100 [thread overview]
Message-ID: <fc94aae90710251209n74e2cffbj2e3cdd321f36da0d@mail.gmail.com> (raw)
In-Reply-To: <20071025185022.GP30533@stusta.de>
Actually I changed the Makefile.cpu and changed the -march to native
which did slightly change the size of the kernel (slightly larger I
think)
So what else does that option change?
Mike
On 25/10/2007, Adrian Bunk <bunk@kernel.org> wrote:
> On Thu, Oct 25, 2007 at 07:33:35PM +0100, Michael Lothian wrote:
> > Hi
> >
> > I was wondering if it was possible to add -march=native support to the
> > processor options of the new x86 architecture if gcc 4.2 or greater is being
> > used.
> >
> > I'm not suggesting this should be a default at all, merely an extra option
> > similar to selecting P4, Athlon or even -Os.
> >
> > I've manually tried this flag at home with no ill effects.
>
> Selecting your CPU in the kernel configuration has more effects than
> just setting the gcc flag, so it wouldn't gain you anything since you
> anyway have to choose the correct CPU.
>
> > Mike
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2007-10-25 19:10 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 ` Michael Lothian
2007-10-25 18:50 ` Adrian Bunk
2007-10-25 19:09 ` Michael Lothian [this message]
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
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=fc94aae90710251209n74e2cffbj2e3cdd321f36da0d@mail.gmail.com \
--to=mike@fireburn.co.uk \
--cc=bunk@kernel.org \
--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
Powered by JetHome