From: Jeff Dike <jdike@addtoit.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: user-mode-linux-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: UML and fastcall/FASTCALL
Date: Fri, 8 Dec 2006 11:33:04 -0500 [thread overview]
Message-ID: <20061208163304.GA5944@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20061208125928.GA25427@stusta.de>
On Fri, Dec 08, 2006 at 01:59:28PM +0100, Adrian Bunk wrote:
> UML on i386 is now the only case where fastcall/FASTCALL is not a noop.
If i386 doesn't use it any more, then UML shouldn't either. The only reason
there's support for it in UML is that I was copying i386.
Jeff
--
Work email - jdike at linux dot intel dot com
next prev parent reply other threads:[~2006-12-08 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 12:59 UML and fastcall/FASTCALL Adrian Bunk
2006-12-08 16:33 ` Jeff Dike [this message]
2006-12-08 18:04 ` 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=20061208163304.GA5944@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=bunk@stusta.de \
--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