From:	Nate Eldredge <neldredge AT hmc DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: inefficiency of GCC output code & -O problem
Date:	17 Apr 2000 12:46:09 -0700
Organization:	InterWorld Communications
Lines:	13
Message-ID:	<83snwktsse.fsf@mercury.st.hmc.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000413112851 DOT 28180G-100000 AT is> <38F6137B DOT 47481761 AT mtu-net DOT ru> <8d76dk$dg5$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <38F74CD0 DOT 6987E15A AT mtu-net DOT ru> <8dep4b$g5f$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <38FAF400 DOT 1B7FE2E6 AT mtu-net DOT ru>
NNTP-Posting-Host:	mercury.st.hmc.edu
Mime-Version:	1.0
X-Trace:	nntp1.interworld.net 956001039 90389 134.173.45.219 (17 Apr 2000 19:50:39 GMT)
X-Complaints-To:	usenet AT nntp1 DOT interworld DOT net
NNTP-Posting-Date:	17 Apr 2000 19:50:39 GMT
User-Agent:	Gnus/5.0802 (Gnus v5.8.2) Emacs/20.5
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"Alexei A. Frounze" <alex DOT fru AT mtu-net DOT ru> writes:

> Also Watcom C/C++ has one very feature. It can generate code for
> register and stack based calling conventions. I.e. parameters may be
> passed either via stack or via registers. It also helps greatly.

GCC can do this.  Look up `regparm' in the Function Attributes section
of the gcc manual.

-- 

Nate Eldredge
neldredge AT hmc DOT edu

- Raw text -