From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: i386: gcc & asm(): wrong constraint for "mull"
Date: Fri, 29 Dec 2000 10:54:38 +0100 [thread overview]
Message-ID: <3A4C6D64.17348.73812@localhost> (raw)
Hello,
I noticed (with some inspiration from Andy Kleen) that some asm()
instructions for the ia32 use the "g" constraint for "mull", where my
Intel 386 Assembly Language Manual suggests the "MUL" instruction needs
an r/m operand. So I guess the correct constraint is "rm" in gcc, and
not "g". That change identical assembly output for gcc-2.95.2, but some
gcc-2.96.x will try a multiplication with an immediate (constant)
operand for the "g" constarint, and the as will choke on that.
(Redhat 7.0 ships such a version of gcc).
As I won't be online next week, let me say
regards and a good new year to all!
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-29 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 9:54 Ulrich Windl [this message]
2000-12-29 10:17 ` i386: gcc & asm(): wrong constraint for "mull" Jakub Jelinek
2000-12-29 10:30 ` Ulrich Windl
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=3A4C6D64.17348.73812@localhost \
--to=ulrich.windl@rz.uni-regensburg.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox