> 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 app
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).
FX
> I am testing trunk on darwin14 (M
Hi,
I am testing trunk on darwin14 (Mac OS X Yosemite), and I am seeing a lot of
(800 so far) C++ failures, in the form of internal compiler errors, like this:
> vbase1.C:17:1: error: unrecognizable insn:
> }
> ^
> (call_insn/j 4 3 5 (call (mem/u/c:DI (const:DI (unspec:DI [
>
