Hi! On Wed, May 18, 2022 at 10:07:48PM +0800, Kewen.Lin wrote: > As PR103353 shows, we may want to continue to expand a MMA built-in > function like a normal function, even if we have already emitted > error messages about some missing required conditions. As shown in > that PR, without one explicit mov optab on OOmode provided, it would > call emit_move_insn recursively.
First off: lxvp is a VSX insn, not an MMA insn. So please don't call it that -- this confusion is what presumably caused the problem here, so it would be good to root it out :-) > + /* Opaque modes are only expected to be available when MMA is supported, Why do people expect that? It is completely wrong. The name "opaque" itself already says this is not just for MMA, but perhaps more importantly, it is a basic VSX insn, doesn't touch any MMA resources, and is useful in other contexts as well. So this needs some bigger surgery. Segher
