public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dacut at neolinear dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/10153] [3.3/3.4 regression] selection of %dil or %sil on ia32 by valid C source
Date: Sat, 14 Feb 2004 04:22:00 -0000 [thread overview]
Message-ID: <20040214042257.19778.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030319173600.10153.etienne.lorrain@masroudeau.com>
------- Additional Comments From dacut at neolinear dot com 2004-02-14 04:22 -------
After some further discussion on the DragonFly lists and further reading on my
part, I found out that %sil and %dil are the 8-bit equivalents of %al, %bl, etc.
(Watch the light bulb undim in my head here :-)
It would be better if gcc were able to diagnose the problem code better (ensure
that the architecture is valid before emitting a %sil/%dil/%bpl/%spl register)
-- I'll see if I can't ponder on this and propose a small patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153
next prev parent reply other threads:[~2004-02-14 4:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030319173600.10153.etienne.lorrain@masroudeau.com>
2003-06-12 18:18 ` rth@gcc.gnu.org
2003-10-31 22:11 ` pinskia at gcc dot gnu dot org
2004-02-13 15:13 ` dacut at neolinear dot com
2004-02-14 4:22 ` dacut at neolinear dot com [this message]
2005-02-15 23:15 ` pinskia at gcc dot gnu dot org
[not found] <bug-10153-873@http.gcc.gnu.org/bugzilla/>
2006-10-24 16:14 ` pinskia at gcc dot gnu dot org
2007-10-06 7:50 ` schwab at suse dot de
[not found] <bug-10153-4@http.gcc.gnu.org/bugzilla/>
2011-03-30 19:51 ` pinskia at gcc dot gnu.org
2021-07-22 16:15 ` cvs-commit at gcc dot gnu.org
2024-03-23 6:51 ` aoliva at gcc dot gnu.org
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=20040214042257.19778.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).