Ok, I guess I will try setting the length attribute as you describe and see if
it is called at all before hard registers are allocated. Then, I can trace any
usage to see if its important.
Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> Andrew Hutchinson <[EMAIL PROTECTED]> writes:
>
> >
Andrew Hutchinson <[EMAIL PROTECTED]> writes:
> As I say above, the logic already exists as c function. If we could
> call these directly to determine the attribute value, it would be much
> easier!
You can. Use symbol_ref. Again, examples in mips.md. Note how the
default value for the "length
Thank you greatly for the feedback
I took at look at mips.md - and we already use the conditional "length"
for some instruction.
However, some effective AVR instruction lengths are vastly complicated
by operands, length and addressing modes. (After all we emulate 16 and
32 bit operations wit
Andrew Hutchinson <[EMAIL PROTECTED]> writes:
> The alternative, perhaps, would be to set each length attribute
> dynamically in each pattern - if that was possible. But that looks
> like way more work.
That is certainly the best way. Search for "length" in mips.md for
one example of how it can
I am working on AVR port and seek advice of the best way working out
what instructions patterns have been natched to RTL.
This requires adjustment of instruction length to assist branching -
when operands are finally known. Before this, worst case lengths are
used from pattern length attribut
