From: Helge Hafting <helge.hafting@aitel.hist.no>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Matheus Izvekov <mizvekov@gmail.com>,
Chris Wedgwood <cw@f00f.org>,
Christoph Hellwig <hch@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [RFC PATCH (take #2)] i386: kill CONFIG_REGPARM completely
Date: Tue, 23 May 2006 09:55:16 +0200 [thread overview]
Message-ID: <4472BFE4.8000605@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.61.0605220739580.26623@chaos.analogic.com>
linux-os (Dick Johnson) wrote:
>On ix86 there are not enough registers to pass a significant parameter
>list all in registers! Like when you are printk()ing a dotted-quad IP
>address, etc. Registers ESI, EDI, and EBX are precious, that leaves
>EAX, ECX, EDX and possibly EBP for only 4 parameters. You need 5
>for the dotted quad IP address. If the compiler were to use the
>precious registers, the contents need to be saved on the stack.
>That negates any advantage to passing parameters in registers.
>
>
I had the impression that REGPARM in i386 only passed the
first three arguments in registers, putting any further
paramters on the stack?
Ought to help for all those 3-argument or less functions.
Helge Hafting
next prev parent reply other threads:[~2006-05-23 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 2:53 [PATCH] i386: don't consider regparm EXPERIMENTAL anymore Chris Wedgwood
2006-05-20 9:06 ` Christoph Hellwig
2006-05-20 20:13 ` [PATCH] i386: kill CONFIG_REGPARM completely Chris Wedgwood
2006-05-20 21:07 ` Chris Wedgwood
2006-05-20 21:20 ` [RFC PATCH (take #2)] " Chris Wedgwood
2006-05-20 22:00 ` Matheus Izvekov
2006-05-20 23:24 ` Chris Wedgwood
2006-05-22 11:47 ` linux-os (Dick Johnson)
2006-05-23 7:55 ` Helge Hafting [this message]
2006-05-24 20:36 ` H. Peter Anvin
2006-05-29 19:03 ` [PATCH] i386: don't consider regparm EXPERIMENTAL anymore Adrian Bunk
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=4472BFE4.8000605@aitel.hist.no \
--to=helge.hafting@aitel.hist.no \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=linux@dominikbrodowski.net \
--cc=mizvekov@gmail.com \
--cc=torvalds@osdl.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