aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2016-02-22 22:27:08 +0100
committerJakub Jelinek <jakub@gcc.gnu.org>2016-02-22 22:27:08 +0100
commit78250306ccc6a32aa473beab781457e2161db607 (patch)
tree336be7f6b64bbd752806c646d2545eeb246d6733 /gcc/doc
parent111f00ed68bd527c16a15758100f314bac9b6aa8 (diff)
downloadgcc-78250306ccc6a32aa473beab781457e2161db607.zip
gcc-78250306ccc6a32aa473beab781457e2161db607.tar.gz
gcc-78250306ccc6a32aa473beab781457e2161db607.tar.bz2
re PR bootstrap/69885 (ICE in maybe_legitimize_operand, at optabs.c:6903 on m68k-linux-gnu)
PR target/69885 * doc/md.texi (ashl@var{m}3): Document that mode of operand 2 must be specified. From-SVN: r233613
Diffstat (limited to 'gcc/doc')
-rw-r--r--gcc/doc/md.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index f9ecfce..4c83719 100644
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -5283,7 +5283,9 @@ Arithmetic-shift operand 1 left by a number of bits specified by operand
2, and store the result in operand 0. Here @var{m} is the mode of
operand 0 and operand 1; operand 2's mode is specified by the
instruction pattern, and the compiler will convert the operand to that
-mode before generating the instruction. The meaning of out-of-range shift
+mode before generating the instruction. The shift or rotate expander
+or instruction pattern should explicitly specify the mode of the operand 2,
+it should never be @code{VOIDmode}. The meaning of out-of-range shift
counts can optionally be specified by @code{TARGET_SHIFT_TRUNCATION_MASK}.
@xref{TARGET_SHIFT_TRUNCATION_MASK}. Operand 2 is always a scalar type.