Re: thin linking: "file is not of required architecture"
Re: thin linking: "file is not of required architecture"
- Subject: Re: thin linking: "file is not of required architecture"
- From: Jeffrey Oleander <email@hidden>
- Date: Tue, 22 Apr 2008 10:24:41 -0700 (PDT)
> Steve Checkoway <email@hidden> wrote:
>> On 2008 Apr 21, at 09:08, Sherm Pendley wrote:
>> Calling conventions are a mix of hardware and
>> language specification.
>>
>> The hardware specifies how the stack frame is
>> arranged, how parameters are passed, and
>> return values returned.
>
> Right.
Parameter passing doesn't even need to use a stack.
Individual arguments/parameters don't have to be
pushed and popped.
OTOH, a "calling stack" may be implicit in the language
in the sense of supporting re-entry, being able
to trace the routine back to the routine that
called it... back to main or whatever.
All this stuff is convention at one level or another,
though hardware capabilities encourage compiler
designers to use certain conventions, and those
conventions have affected how languages are
designed, and so on, and back around with
language designs encouraging the hardware
designers to include certain capabilities.
None of it is "standard" but merely "convention".
So, the question is, "Where are the conventions
documented for the stuff (the combination of
hardware, assembler/compiler, loader) I'm
using in this case?", i.e. which FMs do we
need to read?
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden