This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug inline-asm/5426] Documentation/Behavior differ for array ids in inline asm
- From: "falk at debian dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Jun 2003 17:37:13 -0000
- Subject: [Bug inline-asm/5426] Documentation/Behavior differ for array ids in inline asm
- References: <20020118065600.5426.aliberi@acutronic.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5426
------- Additional Comments From falk@debian.org 2003-06-09 17:37 -------
I am having some problems with your terminology. The C standard
defines "lvalue" as "an expression with an object type or an
incomplete type other than void" and "rvalue" as "value of an
expression". Therefore, an array identifier is both an lvalue and an
rvalue. When you say "lvalue", you probably mean "modifiable lvalue",
and with "rvalue" you seem to mean "non-lvalue". Please clarify.
Also, recently non-lvalues as input memory constraints have been
deprecated, so for example asm ("" : : "m"(1)) and
asm ("" : : "m"(&foo)) won't be accepted any more. Does that suffices
to close this bug in your opinion?