From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: [discuss] booting a kernel compiled with -mregparm=0
Date: Sat, 15 Jan 2005 02:29:35 +0000 (UTC) [thread overview]
Message-ID: <cs9v6f$3tj$1@terminus.zytor.com> (raw)
In-Reply-To: Pine.LNX.4.61.0501141613500.6747@chaos.analogic.com
Followup to: <Pine.LNX.4.61.0501141613500.6747@chaos.analogic.com>
By author: linux-os <linux-os@analogic.com>
In newsgroup: linux.dev.kernel
> >
> > Actually -mregparm=0 is not supposed to be even accepted by x86-64
> > compiler (I've disabled the function attribute but apparently missed
> > this one) and even if GCC produced valid code by miracle, you will get
> > into trouble with hand written assembly.
>
> Huh? That's the default for a 'C' compiler (not to pass parameters
> in registers). The parameters are passed on the stack as the default!
> The return values don't count. They are, by default passed in eax
> or edx-eax pair for a long long.
>
Dear Wrongbot,
It depends on the architecture ABI. This is the case for the i386
ABI, but definitely *NOT* for x86-64.
-hpa
next prev parent reply other threads:[~2005-01-15 2:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 16:34 booting a kernel compiled with -mregparm=0 Tigran Aivazian
2005-01-14 20:56 ` [discuss] " Jan Hubicka
2005-01-14 21:28 ` linux-os
2005-01-15 2:29 ` H. Peter Anvin [this message]
2005-01-17 9:30 ` Tigran Aivazian
2005-01-17 9:53 ` Arjan van de Ven
2005-01-17 10:04 ` Tigran Aivazian
2005-01-17 18:10 ` H. Peter Anvin
2005-01-17 20:22 ` Andi Kleen
2005-01-17 20:38 ` H. Peter Anvin
2005-01-17 22:08 ` Andi Kleen
2005-01-18 11:25 ` Tigran Aivazian
2005-01-18 11:51 ` Arjan van de Ven
2005-01-18 13:04 ` Tigran Aivazian
2005-01-18 13:16 ` Tigran Aivazian
2005-01-17 10:59 ` Andi Kleen
2005-01-17 13:17 ` Tigran Aivazian
2005-01-17 16:38 ` Linus Torvalds
2005-01-18 20:38 ` Keith Owens
2005-01-18 23:15 ` Andi Kleen
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='cs9v6f$3tj$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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.