> In fact, after looking at the latest gcc-patches messages, I think it may be > due to this commit: https://gcc.gnu.org/ml/gcc-patches/2014-09/msg01107.html > (based purely on the fact that the unrecognized insn is a call, and the patch > deals with CALL_EXPR).
Duh. No, it’s not, cause it’s apparently not committed yet (at least, not in rev. 215234 which is the one failing for me). But now, I’ve found it is PR 61387 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61387), already known. FX
