dTo: unassigned at gcc dot gnu dot org
ReportedBy: mrd at alkemio dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i386-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22448
--- Additional Comments From mrd at alkemio dot org 2005-05-17 00:33
---
(In reply to comment #8)
> Did you read comment #1.
Yes, but it's not clear.
> GCC doesn't know what constitutes a reference to a volatile memory
Is this to say the GCC developers believe
--- Additional Comments From mrd at alkemio dot org 2005-05-16 22:34
---
(In reply to comment #5)
> Mark as invalid.
Why?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3506
ssigned at gcc dot gnu dot org
ReportedBy: mrd at alkemio dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21580
--- 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 +, pinskia at gcc dot gnu dot org wrote:
> You don't want the "al" contstraint at all.
>
>
--- Additional Comments From mrd at alkemio dot org 2005-03-05 06:44
---
Subject: Re: assembly constraints fail unless optimizing code
On Sat, 2005-03-05 at 01:26 +, giovannibajo at libero dot it wrote:
> Which target triplet?
i386-pc-linux-gnu
--
http://gcc.gnu.
in `asm'
foo.c:9: error: impossible constraint in `asm'
$ gcc -c foo.c -O
$
--
Summary: assembly constraints fail unless optimizing code
Product: gcc
Version: 3.4.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
A
