From: Richard Henderson <rth@twiddle.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: ja@himel.com, linux-kernel@vger.kernel.org
Subject: Re: cpuid_eax damages registers (2.4.7pre7)
Date: Sat, 21 Jul 2001 16:45:44 -0700 [thread overview]
Message-ID: <20010721164544.B3676@twiddle.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10107181347030.16710-100000@l> <200107181510.f6IFAMW03662@penguin.transmeta.com>
In-Reply-To: <200107181510.f6IFAMW03662@penguin.transmeta.com>; from torvalds@transmeta.com on Wed, Jul 18, 2001 at 08:10:22AM -0700
On Wed, Jul 18, 2001 at 08:10:22AM -0700, Linus Torvalds wrote:
> - fix _all_ the "cpuid*()" functions to have
>
> :"0" (op)
>
> instead of their current incorrect
>
> :"a" (op)
>
> (we're supposed to explicitly tell the compiler that the first input
> is the same as the first output)
FWIW, using "a" as the input constraint isn't incorrect.
The two are equivalent given a singleton register class.
r~
next prev parent reply other threads:[~2001-07-21 23:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 10:48 cpuid_eax damages registers (2.4.7pre7) Julian Anastasov
2001-07-18 15:10 ` Linus Torvalds
2001-07-18 17:08 ` Julian Anastasov
2001-07-18 17:21 ` Linus Torvalds
2001-07-18 20:43 ` Kai Germaschewski
2001-07-18 22:04 ` Linus Torvalds
2001-07-18 22:25 ` Kai Germaschewski
2001-07-19 8:23 ` Julian Anastasov
2001-07-19 18:36 ` H. Peter Anvin
2001-07-20 1:42 ` Julian Anastasov
2001-07-19 22:51 ` H. Peter Anvin
2001-07-20 2:01 ` Julian Anastasov
2001-07-19 23:02 ` H. Peter Anvin
2001-07-19 22:55 ` Linus Torvalds
2001-07-20 2:19 ` Julian Anastasov
2001-07-19 23:23 ` H. Peter Anvin
2001-07-19 23:24 ` Linus Torvalds
2001-07-22 0:00 ` Richard Henderson
2001-07-22 4:27 ` H. Peter Anvin
2001-07-21 23:45 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-18 20:30 Rick Hohensee
2001-07-19 5:15 ` Keith Owens
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=20010721164544.B3676@twiddle.net \
--to=rth@twiddle.net \
--cc=ja@himel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.