All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] i386: enable REGPARM by default
Date: 15 May 2005 15:00:08 +0200
Date: Sun, 15 May 2005 15:00:08 +0200	[thread overview]
Message-ID: <20050515130008.GA72644@muc.de> (raw)
In-Reply-To: <20050515123729.GT16549@stusta.de>

On Sun, May 15, 2005 at 02:37:31PM +0200, Adrian Bunk wrote:
> On Sun, May 15, 2005 at 02:22:34PM +0200, Andi Kleen wrote:
> > Adrian Bunk <bunk@stusta.de> writes:
> > 
> > > This patch should _not_ go into Linus' tree.
> > >
> > > At some time in the future, we want to unconditionally enable REGPARM on 
> > > i386.
> > >
> > > Let's give it a bit broader testing coverage among -mm users.
> > 
> > iirc problem is that gcc 2.95 and possibly 3.0.x have some known
> > miscompilations with regparams. That is why it was only used
> > with fastcall for a long time. One 3.1.x+ it should be safe.
> > But you cannot express dependencies on the compiler version
> > in Kconfig right now.
> > 
> > Of course getting rid of gcc 2.95 and 3.0.x support would be a good idea,
> > that would allow many other nice things.
> 
> If you'd read either arch/i386/Makefile or the help text for 
> CONFIG_REGPARM, you'd have noticed that we do never use regparm with
> gcc < 3.0 .

Yes, this means you cannot have binary compatible kernels compiled
with different compilers. Which might be a bad thing.  For that
reason alone I would keep the config.

-Andi

  reply	other threads:[~2005-05-15 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 11:57 [-mm patch] i386: enable REGPARM by default Adrian Bunk
2005-05-15 12:22 ` Andi Kleen
2005-05-15 12:37   ` Adrian Bunk
2005-05-15 13:00     ` Andi Kleen [this message]
2005-05-15 13:12       ` Arjan van de Ven
2005-05-15 13:16       ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2005-05-30  0:28 Adrian Bunk
2005-06-24 20:09 Adrian Bunk
2005-06-24 20:28 ` Andrew Morton
2005-06-25  7:46 ` Denis Vlasenko
2005-06-28 12:16   ` Jens Axboe

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=20050515130008.GA72644@muc.de \
    --to=ak@muc.de \
    --cc=bunk@stusta.de \
    --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 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.