Re: [Linux-ia64] ld-linux.so

[Jes Sorensen <Jes.Sorensen@cern.ch>]

>>>>> "Jes" = Jes Sorensen <Jes.Sorensen@cern.ch> writes:

>>>>> "Kevin" = Kevin Buettner <kev@primenet.com> writes:
Kevin> On Apr 23, 11:02am, Jes Sorensen wrote:
>>> I know very little about the C++ ABI so this may be C++ specific.
>>> I thought r8 was meant to be a return register and not an input
>>> register and that it's valid to clobber it in any function call,
>>> whether the function returns a value or void?

Kevin> When the function in question returns an (non-HFA) aggregate
Kevin> that's larger than 32 bytes (256 bits), r8 is an input register
Kevin> containing the address of the region of memory into which to
Kevin> write the return structure.  When this is the case, r8 is not
Kevin> an output register.  I.e, the calling conventions do not
Kevin> mandate restoring the struct address.

Jes> ARGH!

Jes> Thats nasty, I would much have preferred to see something like
Jes> r32 used as the input pointer and have it returned in r8
Jes> afterwards. This way it is going to cause overhead on every
Jes> single lookup ;-(

Hmmm ok, a bit of overreacting since we can store r8 in a local
register, we don't need to flush it onto the stack as I was thinking
at first.

However, I just checked the code and r8 is already being saved in loc2
across the lookup call. I suspect this was put in when Richard
Henderson optimized the packaging of the bundles.

Jes