[aarch64-port-dev ] aarch64 port "review"

[Roland Westrelin]

Hi Ed,

Thanks for your comments.

> Compiler traffic is more under our contros. The main source of
> compiler generated traffic is inter procedural, IE spilling of
> registers and the frame overhead (128 bits). One thing I have
> considered is whether moving to a mixed caller/callee convention as
> per C/C++ would gain us anything. However here be dragons (I think
> there are even comments in the source to warn about the dragons). How
> could we estimate what the benefit of moving to a mixed caller/callee
> convention would be without actually doing it.

Indeed, switching to a caller/callee convention doesn't sound like a
small piece a work.

Wouldn't the fact that c2 inlines a lot (it can devirtualize calls)
makes a caller/callee calling convention less beneficial than with c++?
Presumably, if a method is not inlined it's because it's big (a lot of
time is spent there) so extra spill/restore around the call wouldn't
matter?

Roland.