Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!wuarchive!uunet!sobeco!onfcanim!zap!matrox!uvm-gen!kira!emily!wollman
From: wollman@emily.uvm.edu (Garrett Wollman)
Newsgroups: comp.lang.c
Subject: Re: cdecl and pascal keywords
Message-ID: <1991Jan1.181041.9444@uvm.edu>
Date: 1 Jan 91 18:10:41 GMT
References: <26075@uflorida.cis.ufl.EDU> <1990Dec27.042434.16584@ <898@tuura.UUCP>
Sender: news@uvm.edu
Organization: University of Vermont - EMBA Computing Facility
Lines: 25
Raymond-Protection: enabled

We are getting *very* far afield from the subject of C... :-(

That said, I should point out to the previous posters, that there is
*no* reason why the arguments have to be popped off the stack
immediately after every function call.  In fact, by default, gcc -O
waits to pop until there is a branch or unbranch in control-flow (or,
at any rate, that what I *think* it's doing) before popping.  You have
to specifically request -fno-defer-pop for it to stop doing this.

Of course, you can also do without a frame pointer if it strikes your
fancy--just don't try to debug!

Unfortunately, as all PC programmers know, Microsoft is (and always
has been) considerably behind the times when it comes to optimization.
I'm thinking of trying to compile the mutated, 16-bit, 8086-supporting
version of GCC so that I can get decent optimization on PC programs.
I'm also thinking of scrapping PC programming altogether, at least so
long as I have access to a Real Computer :-)

-GAWollman

Garrett A. Wollman - wollman@emily.uvm.edu

Disclaimer:  I'm not even sure this represents *my* opinion, never
mind UVM's, EMBA's, EMBA-CF's, or indeed anyone else's.