All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPU type .config <-> i386/Makefile question[s]
Date: Sun, 5 Jun 2005 19:43:22 +0200	[thread overview]
Message-ID: <20050605174322.GF4992@stusta.de> (raw)
In-Reply-To: <200506051458.50307.nick@linicks.net>

On Sun, Jun 05, 2005 at 02:58:50PM +0100, Nick Warne wrote:

> Hello all,

Hi Nick,

> I am still a n00b here learning, so by all means tell me to get lost if what I 
> am about to say is total bollocks...
> 
> I was just running through building the new 2.4.31 kernel on my Quake2 box, 
> with looking at building this time with a few optimisations.
>...
> Is there a specific reason why the flags aren't -march=pentium2, pentiumpro 
> etc?

the specific reason is that kernel 2.4 is in a maintainance mode and 
such changes are not considered being worth the risk of breaking 
anything anywhere with any of the supported gcc versions.

In kernel 2.6, this is already handled the way you expect it.

> Also I notice that if I changed the top level Makefile to include my specific 
> CPU, then the i386/Makefile adds += -march=i686 to the build lines AFTER 
> CFLAGS~ thus the second one will take precedence (I guess) anyway, and the 
> -march CFLAG changes are basically over-ridden?

Users are not expected to manually set any CFLAGS.

It might work in your case, but unless you _really_ know what you are 
doing you always risk some breakage.

> Regards,
> 
> Nick

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


  reply	other threads:[~2005-06-05 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 13:58 CPU type .config <-> i386/Makefile question[s] Nick Warne
2005-06-05 17:43 ` Adrian Bunk [this message]
2005-06-05 19:43   ` Nick Warne

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=20050605174322.GF4992@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    /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.