Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!megatest!djones
From: djones@megatest.UUCP (Dave Jones)
Newsgroups: comp.lang.c
Subject: Re: C optimizer
Message-ID: <2008@goofy.megatest.UUCP>
Date: 16 Feb 89 03:56:35 GMT
References: <1398@quanta.eng.ohio-state.edu>
Organization: Megatest Corporation, San Jose, Ca
Lines: 21

From article <1398@quanta.eng.ohio-state.edu>, by rob@kaa.eng.ohio-state.edu (Rob Carriere):

> 
> What seems to be missing is the idea that sleep *does* modify
> something, namely time.  So formally speaking, your compiler should
> consider sleep to have a side effect on a variable called __time.  If
> you do that, there's no problem.
> 


Huh?? 

% nm a.out | grep __time
%

Know what I mean?

On a time-shared system (such as Unix), does every instruction have
a side effect on a variable called __time?

Gimme a break.  (Or at least a sleep(300).)