[fpc-devel] max_operands for AVR after rev 40170

[Christo Crause]

On Fri, Nov 2, 2018 at 12:51 PM Pierre Muller <pierre at freepascal.org> wrote:

> Hopefully someone else can explain that discrepancy,
> I have no idea why this exists,
> it might be simply related to the CPU instructions
> with most parameters that are considered for optimization!
>

Thanks for the backgroup Pierre.  I've changed max_operands = 2 for AVR
(and updated AVRInstrConstraint in raavr.pas), recompiled the crossavr
compiler and RTL for avr5 and preliminary inspection show correct code
being generated.  Perhaps these two constants (MaxOps and ax_operands)
should be merged if there isn't a difference in meaning and use case
between them?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20181103/ee091942/attachment.html>