Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!apple!agate!helios.ee.lbl.gov!nosc!cod!mball
From: mball@cod.NOSC.MIL (Michael S. Ball)
Newsgroups: comp.lang.c
Subject: Re: Short code to determine compiler's
Message-ID: <1585@cod.NOSC.MIL>
Date: 23 Jul 89 16:36:05 GMT
References: <396@uop.uop.EDU> <225800197@uxe.cso.uiuc.edu> <579@targon.UUCP> <171@bms-at.UUCP> <14497@dartvax.Dartmouth.EDU> <1038@cernvax.UUCP>
Reply-To: mball@cod.nosc.mil.UUCP (Michael S. Ball)
Organization: Naval Ocean Systems Center, San Diego
Lines: 21

In article <1038@cernvax.UUCP> hjm@cernvax.UUCP (Hubert Matthews) writes:
>
>I have a question for the authors of smart C compilers: is the
>register declaration useful at all for such compilers?

I can only speak for the three compilers with which I have been intimate,
but in them the "register" declaration had no effect except to prohibit
the application of "&".  In one of them you could force the compiler
to take your advice and pay attention to the "register" declaration.  It
usually only slowed the code a little bit.

Personally, I think compilers which require register declarations should
be referred to as "dumb C compilers", rather than referring to modern
compilers as "smart C compilers".

Michael S. Ball
TauMetric Corporation
1094 Cudahy Place, Ste 302
San Diego, CA 92110
(619)275-6381
mball@cod.nosc.mil