Related articles |
---|
register variables in C. eric@pencom.com (1992-04-22) |
register variables in C. kennykb@dssv01.crd.ge.com (1992-04-22) |
Re: register variables in C. moss@cs.umass.edu (1992-04-23) |
Re: register variables in C. dd@mips.com (1992-04-23) |
Re: register variables in C. dave.howell@ColumbiaSC.NCR.COM (Dave Howell) (1992-04-24) |
Re: register variables in C. bart@cs.uoregon.edu (1992-04-29) |
Re: register variables in C. jeff@dsp.sps.mot.com (1992-04-30) |
Re: register variables in C. Brian.Scearce@Eng.Sun.COM (1992-04-30) |
Re: register variables in C. pardo@cs.washington.edu (1992-05-01) |
Re: register variables in C. metaware!miker@uunet.UU.NET (1992-05-01) |
Re: register variables in C. preston@dawn.cs.rice.edu (1992-05-01) |
Re: register variables in C. bliss@sp64.csrd.uiuc.edu (1992-05-01) |
Re: register variables in C. ressler@cs.cornell.edu (1992-05-02) |
[4 later articles] |
Newsgroups: | comp.compilers |
From: | jeff@dsp.sps.mot.com (Jeff Enderwick) |
Keywords: | C, registers, optimize |
Organization: | Motorola DSP Compilers |
References: | 92-04-125 92-04-161 |
Date: | Thu, 30 Apr 1992 12:24:29 GMT |
>Perhaps the best thing for now would be for C compiler vendors to
>agree on a name for a pragma which would make their allocators honor
>explicit register declarations wherever possible...
One problem with using register is that different CPUs have different
numbers and types of registers. When you write "portable" C, assuming that
compilers respect the register modifier, you need to worry about using
"register" too few or too many times. Maybe we should dump "register" and
add branch hints. If a compiler only counted likely uses of variables,
then it might just promote the best variables.
Jeff Enderwick
jeff@dsp.sps.mot.com
[Hmmn. Branch hints, dating back to the Fortran I FREQUENCY statement, have
not had a particularly illustrious history, either. -John]
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.