This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH][M68K] Fix extendsidi pattern to handle ColdFire
Maxim Kuvyrkov wrote:
Operand3 was introduced for the sake of making output code cleaner;
operands = adjust_address (operands, SImode,
which_alternative == 0 ? 4 : 0);
While this construct has been working without declaring the operand in
the pattern for years, it is cleaner, in my opinion, to explicitly
declare every operand in use by the pattern.
I don't think that's true at all. Not for derived operands like this.