Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!pilchuck!dataio!bright
From: bright@Data-IO.COM (Walter Bright)
Newsgroups: comp.lang.c
Subject: Re: Compilers and programming style (was Re: A question of style)
Message-ID: <2288@dataio.Data-IO.COM>
Date: 10 Jan 90 18:54:20 GMT
References: <1989Dec22.100135.2903@gdt.bath.ac.uk> <4367@rtech.rtech.com> <1989Dec31.153241.16479@gdt.bath.ac.uk> <649@codonics.COM> <1990Jan5.100042.26760@gdt.bath.ac.uk> <2283@dataio.Data-IO.COM> <534@bbxsda.UUCP>
Reply-To: bright@dataio.Data-IO.COM (Walter Bright)
Organization: Data I/O Corporation; Redmond, WA
Lines: 9

In article <534@bbxsda.UUCP> scott@bbxsda.UUCP (Scott Amspoker) writes:
<In article <2283@dataio.Data-IO.COM> bright@dataio.Data-IO.COM (Walter Bright) writes:
<<volatile int *p;
<<*p;		/* has side effects and must not be optimized away	*/
<Just curious - what kind of code should be generated for the above C fragment?

Should be something like:
	MOV BX,p
	MOV AX,[BX]