aboutsummaryrefslogtreecommitdiff
path: root/gas/doc
diff options
context:
space:
mode:
authorNick Clifton <nickc@redhat.com>1998-02-13 21:52:13 +0000
committerNick Clifton <nickc@redhat.com>1998-02-13 21:52:13 +0000
commit8e7a5a048aa35777f3a69fd0ba9d29bb5541138a (patch)
treef2b07d6e4aa8dfe9f13557865d8ba6db24d94ca3 /gas/doc
parentba4da4fe4e8c040302f11a210c1bd3cc23b7e4b2 (diff)
downloadgdb-8e7a5a048aa35777f3a69fd0ba9d29bb5541138a.zip
gdb-8e7a5a048aa35777f3a69fd0ba9d29bb5541138a.tar.gz
gdb-8e7a5a048aa35777f3a69fd0ba9d29bb5541138a.tar.bz2
Reverted writes_to_pc() back to old version of code until PC operands are
supported by cgen.
Diffstat (limited to 'gas/doc')
-rw-r--r--gas/doc/c-m32r.texi29
1 files changed, 6 insertions, 23 deletions
diff --git a/gas/doc/c-m32r.texi b/gas/doc/c-m32r.texi
index 082820b..df36aaa 100644
--- a/gas/doc/c-m32r.texi
+++ b/gas/doc/c-m32r.texi
@@ -70,7 +70,7 @@ There are several warning and error messages that can be produced by
@table @code
-@item output of first instruction is the same as the input of second instruction - is this intentional ?
+@item output of 1st instruction is the same as an input to 2nd instruction - is this intentional ?
This message is only produced if warnings for explicit parallel
conflicts have been enabled. It indicates that the assembler has
encountered a parallel instruction in which the destination register of
@@ -79,7 +79,7 @@ instruction. For example in this code fragment
@samp{mv r1, r2 || neg r3, r1} register r1 is the destination of the
move instruction and the input to the neg instruction.
-@item output of second instruction is the same as the input of first instruction - is this intentional ?
+@item output of 2nd instruction is the same as an input to 1st instruction - is this intentional ?
This message is only produced if warnings for explicit parallel
conflicts have been enabled. It indicates that the assembler has
encountered a parallel instruction in which the destination register of
@@ -109,31 +109,14 @@ executed in parallel.
This message is produced when the assembler encounters a parallel
instruction whoes components both use the same execution pipeline.
-@item Both instructions write to the link register
-This message is produced when the assembler encounters a parallel
-instruction whoes components both write to the link register, one of
-them as a side effect. For example this code fragment will produce this
-message: @samp{jl r0 || mv r14, r1}
-
-@item Destination of first instruction written to by side effect of second instruction.
-This message is produced when the assembler encounters a parallel
-instruction whoes right hand component has a side effect which modifes a
-register used as the destination by the left hand component. For
-example this code fragment will produce this message:
-@samp{mv r1, r2 || ld r0, @@r1+}
-
-@item Destination of second instruction written to by side effect of first instruction.
-This message is produced when the assembler encounters a parallel
-instruction whoes left hand component has a side effect which modifes a
-register used as the destination by the right hand component. For
-example this code fragment will produce this message:
-@samp{st r2, @@-r1 || mv r1, r3}
-
@item Instructions write to the same destination register.
This message is produced when the assembler encounters a parallel
instruction where both components attempt to modify the same register.
-For example this code fragment will produce this message:
+For example these code fragments will produce this message:
@samp{mv r1, r2 || neg r1, r3}
+@samp{jl r0 || mv r14, r1}
+@samp{st r2, @@-r1 || mv r1, r3}
+@samp{mv r1, r2 || ld r0, @@r1+}
@end table
@c end-sanitize-m32rx