public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mrd at alkemio dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/20328] assembly constraints fail unless optimizing code
Date: Sat, 05 Mar 2005 06:52:00 -0000 [thread overview]
Message-ID: <20050305065253.6630.qmail@sourceware.org> (raw)
In-Reply-To: <20050305011918.20328.mrd@alkemio.org>
------- Additional Comments From mrd at alkemio dot org 2005-03-05 06:52 -------
Subject: Re: assembly constraints fail unless optimizing code
On Sat, 2005-03-05 at 01:31 +0000, pinskia at gcc dot gnu dot org wrote:
> You don't want the "al" contstraint at all.
>
> Read the docs to figure out which constaint you really want. the constraint "al" means pick either the
> "a" constraint or the "l" constraint
The original code's not mine at all, so I don't know what constraint is
actually wanted. However, after looking through section 5.36 of the gcc
3.4.3 manual, I can't figure out what the "l" constraint means for the
i386 architecture anyways.
So maybe the original code *shouldn't* be using the "=al" constraint,
but either the manual's missing a description of the "l" constraint for
i386 so I can't decide whether it's correct or not, or gcc's not
complaining about an illegal constraint when optimizations are enabled
(or maybe that's an optimization feature?).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20328
prev parent reply other threads:[~2005-03-05 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 1:19 [Bug c/20328] New: " mrd at alkemio dot org
2005-03-05 1:26 ` [Bug c/20328] " giovannibajo at libero dot it
2005-03-05 1:31 ` pinskia at gcc dot gnu dot org
2005-03-05 6:44 ` mrd at alkemio dot org
2005-03-05 6:52 ` mrd at alkemio dot org [this message]
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=20050305065253.6630.qmail@sourceware.org \
--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).