SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD) -- Ignore unavailable to you. Want to Upgrade?


To: pgerassi who wrote (74153)3/10/2002 9:40:35 PM
From: Joe NYCRead Replies (3) | Respond to of 275872
 
Pete, Gottfried,

I looked around a bit and this is what I came up with:
There are 2 popular calling conventions: C and Pascal. Under Pascall calling convention it is the responsibility of the called procedure to adjust or clean the stack. Under C calling convention, caller is responsible for pushing things on stack, and cleaning up afterwards.

Pascal calling convention is most popular, since it is obviously more efficient. Under C calling convention, caller has no knowledge of what's going on in called procedure, so everything needs to be saved.

Under Pascal calling convention, compiler knows what resources are being used in the procedure, so it knows what needs to be saved, so only a subset of all resources needs to be saved on stack.

Joe