On Fri, Aug 13, 2021 at 12:14:14AM -0400, Michael Meissner wrote: > I noticed that the xxeval built-in function used the altivec_register_operand > predicate. Since it takes vsx registers, this might force the register > allocate to issue a move when it could use a traditional floating point > register. This patch fixes that.
Why register_operand instead of gpc_reg_operand? The former allows subregs of memory, likely not what you want here (and not in other rs6000 pattern that currently use it, either). Segher
