🚀 go-pugleaf

The request seems fairly obvious to me.  One writer wrote about how
his line
	n = n;
was necasary for the hardware to work.  I have seen compilers drop that
one on the floor.  There was also some discussion about adding a new
storage class to C named 'volatile' or some so that references of this
seemingly weird type aren't ignored.  The device driver code for some
hardware requires you to read from a silo more than one time to get the
desired peice of information.  If I write

	status = *silo;
	status = *silo;

on a real *smart* compiler, the second assignment may never happen.
I might get real clever and write

	status = *silo;
	status = 0;
	status = *silo;

only to find the first two lines dropped.

If I am stupid enough to write

	n = n;

The compiler should be smart enough to code the turkey.  Compilers
are for compiling, program verifiers are for 'picking the peices of
fluff' from your programs.

- John.

Disclaimer:
	I hold you entirely responsible for what I write.