extend.texi (Extended Asm): Document inability to give asm statements access to condition codes.
* extend.texi (Extended Asm): Document inability to give asm statements access to condition codes. From-SVN: r33709
This commit is contained in:
parent
4edee0e6a1
commit
eda3fbbe7a
@ -1,3 +1,8 @@
|
||||
2000-05-05 Geoff Berry <geoffb@bops.com>
|
||||
|
||||
* extend.texi (Extended Asm): Document inability to give asm
|
||||
statements access to condition codes.
|
||||
|
||||
2000-05-05 Marek Michalkiewicz <marekm@linux.org.pl>
|
||||
|
||||
* varasm.c (asm_emit_uninitialised): Use 0, not NULL
|
||||
|
@ -2678,6 +2678,10 @@ instructions would alter the condition code before there was time to
|
||||
test it. This problem doesn't arise for ordinary ``test'' and
|
||||
``compare'' instructions because they don't have any output operands.
|
||||
|
||||
For reasons similar to those described above, it is not possible to give
|
||||
an assembler instruction access to the condition code left by previous
|
||||
instructions.
|
||||
|
||||
If you are writing a header file that should be includable in ANSI C
|
||||
programs, write @code{__asm__} instead of @code{asm}. @xref{Alternate
|
||||
Keywords}.
|
||||
|
Loading…
Reference in New Issue
Block a user