Mail Archives: djgpp/1996/04/30/10:21:34
Xref: | news2.mv.net comp.os.msdos.djgpp:3274
|
From: | sime AT fly DOT cc DOT fer DOT hr (S. Mikecin)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | register calling convention
|
Date: | 29 Apr 1996 14:44:47 GMT
|
Organization: | none organization
|
Lines: | 16
|
Distribution: | world
|
Message-ID: | <4m2kkv$h7p@bagan.srce.hr>
|
Reply-To: | sime AT fly DOT cc DOT etf DOT hr
|
NNTP-Posting-Host: | fly.cc.etf.hr
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Some of you needed an explanation, well here it is:
When i mention "register calling convention" I mean that compiler uses
registers to store parameters before calling a function, and if that
function returns something it is also return thru the register! It is an
opposite to the "stack calling convention" which means that all parameters
are been pushed on the stack, and result is taken from it. So, question is:
How to tell DJGPP to use "register calling convention"?
In Borland C++ it can be done for a particular user function using reserved
word _fastcall. In Watcom C/C++ it is by default (also works with standard
functions)! But what about DJGPP?
--
<E-mail: sime AT fly DOT cc DOT fer DOT hr >
<URL: http://fly.cc.fer.hr/~sime>
- Raw text -