From 8cb0906b0fa9c07095db1ec7fb22eaeecf5075af Mon Sep 17 00:00:00 2001 From: Segher Boessenkool Date: Wed, 6 Nov 2019 01:06:23 +0100 Subject: [PATCH] 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 --- gcc/ChangeLog | 6 +++++- gcc/doc/md.texi | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 8ee23dd5986..63ef7114b68 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,4 +1,8 @@ -2019-10-26 Jason Merrill +2019-11-05 Segher Boessenkool + + * doc/md.texi (Insn Splitting): Fix combiner documentation. + +2019-11-05 Jason Merrill PR tree-optimization/91825 * expmed.c: Reduce -Wmaybe-uninitialized to warning. diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 859ebed0e9b..19d6893882b 100644 --- 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 -- 2.30.2