Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!rutgers!mit-eddie!husc6!necntc!encore!linus!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.lang.c
Subject: Re: draft ANSI standard: const/volatile functions
Message-ID: <589@mcgill-vision.UUCP>
Date: Sun, 21-Dec-86 03:38:39 EST
Article-I.D.: mcgill-v.589
Posted: Sun Dec 21 03:38:39 1986
Date-Received: Mon, 22-Dec-86 18:42:17 EST
References: <1384@hoptoad.uucp> <4863@ism780c.UUCP>
Organization: McGill University, Montreal
Lines: 19

In article <4863@ism780c.UUCP>, tim@ism780c.UUCP (Tim Smith) writes:
>> * you can declare a function to be const or volatile.

> Hey, this could be nice for [...] code that changes itself.  If a
> function is declared volatile, then the compiler could follow each
> instruction with a "flush instruction cache" instruction.

> I can hardly wait for the next obfuscated C code contest...

Or imagine if the cache-flush is privileged (eg, a VAX: mtpr $TBIA,$0)
and must be done via a syscall.  Inefficiency city....a syscall *every*
*instruction*?!

					der Mouse

USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse
     think!mosart!mcgill-vision!mouse
Europe: mcvax!decvax!utcsri!mcgill-vision!mouse
ARPAnet: think!mosart!mcgill-vision!mouse@harvard.harvard.edu