On 01/14/2017 06:55 PM, Segher Boessenkool wrote:
As shown in the PR, ifcvt will happily make invalid insns when given the
chance. This patch teaches it some manners.
Bootstrapped and tested on powerpc64-linux. Is this okay for trunk?
Segher
2017-01-15 Segher Boessenkool <seg...@kernel.crashing.org>
PR rtl-optimization/78751
* ifcvt.c (find_cond_trap): If we generated a non-existing insn,
give up.
But isn't this a backend failing? ISTM that gen_cond_trap just calls
standard expansion routines and they should either have generated a
valid sequence or NULL.
What in particular generated insn 64 and shouldn't it instead have
indicated a failure?
Jeff
