Brilliant!
This got rid of the warnings, *and* got rid of the spurious move I was getting. Thanks for the advice!
The problem with the spurious move was with the move from memory to the v16sf register, because it was doing it with subregs it thought it still had to preserve the previous (uninitialised) value and so couldn't optimize the move out completely because of the parameter aliasing on those asm instructions.
For the last parameter (equiv) of emit_no_conflict_block I am putting in "gen_rtx_SET ( V16SFmode, op0, op1 )", does this seem correct to you?
Much thanks
Dylan
"James E Wilson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
Dylan Cuthbert wrote:Is there someway I can flag the moves to say that is moving the v16sf "whole" so it doesn't need to be initialised and hence avoid the warning?
See emit_no_conflict_block in optabs.c. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
