doc: Insn splitting by combine

The combine pass is perfectly happy if a splitter splits to just one
instruction (instead of two).

	* doc/md.texi (Insn Splitting): Fix combiner documentation.

From-SVN: r277866

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 8ee23dd5986befbc054c8d53801e098003510449..63ef7114b68ec78654472c92939ddff1388ba659 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,4 +1,8 @@
-2019-10-26  Jason Merrill  <jason@redhat.com>
+2019-11-05  Segher Boessenkool  <segher@kernel.crashing.org>
+
+       * doc/md.texi (Insn Splitting): Fix combiner documentation.
+
+2019-11-05  Jason Merrill  <jason@redhat.com>
 
        PR tree-optimization/91825
        * expmed.c: Reduce -Wmaybe-uninitialized to warning.

diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
index 859ebed0e9b4daaebfe3e52c80042fef3570afc7..19d6893882b77c7c4fce60c0cfd81b792df0dbb3 100644 (file)
--- a/gcc/doc/md.texi
+++ b/gcc/doc/md.texi
@@ -8371,7 +8371,7 @@ case that the pattern is @emph{not} matched by any @code{define_insn}.
 The combiner pass first tries to split a single @code{set} expression
 and then the same @code{set} expression inside a @code{parallel}, but
 followed by a @code{clobber} of a pseudo-reg to use as a scratch
-register.  In these cases, the combiner expects exactly two new insn
+register.  In these cases, the combiner expects exactly one or two new insn
 patterns to be generated.  It will verify that these patterns match some
 @code{define_insn} definitions, so you need not do this test in the
 @code{define_split} (of course, there is no point in writing a