From: Adrian Bunk <bunk@stusta.de>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's?
Date: Tue, 22 Aug 2006 21:28:14 +0200 [thread overview]
Message-ID: <20060822192814.GA19896@stusta.de> (raw)
In-Reply-To: <20060822174233.GA5471@ccure.user-mode-linux.org>
On Tue, Aug 22, 2006 at 01:42:33PM -0400, Jeff Dike wrote:
> On Tue, Aug 22, 2006 at 06:07:41PM +0200, Adrian Bunk wrote:
> > I didn't find a corresponding open bug in the gcc Bugzilla.
> >
> > Can someone verify whether it's still present, and if yes, open a gcc
> > bug?
>
> Yup, it's easy enough to check.
Thanks.
> > It's set globally in arch/i386/Makefile:
> > cflags-$(CONFIG_REGPARM) += -mregparm=3
>
> IIRC, there used to be functions explicitly declared as __regparam or
> something, and that's what I was grepping for. Does this turn every
> function with three or fewer parameters into a regparam function?
>...
With -mregparm=3, the first up to three parameters that aren't bigger
than an integer are passed in registers instead of on the stack.
> Jeff
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
next prev parent reply other threads:[~2006-08-22 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 21:56 arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's? Adrian Bunk
2006-08-22 2:20 ` [uml-devel] " Jeff Dike
2006-08-22 16:07 ` Adrian Bunk
2006-08-22 17:42 ` Jeff Dike
2006-08-22 19:28 ` Adrian Bunk [this message]
2006-08-26 10:56 ` Blaisorblade
2006-08-28 20:35 ` Jeff Dike
2006-08-29 8:26 ` Paolo Giarrusso
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=20060822192814.GA19896@stusta.de \
--to=bunk@stusta.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox