[PATCH] C undefined behavior fix

Alexandre Oliva aoliva@redhat.com
Tue Jan 8 06:03:00 GMT 2002


On Jan  8, 2002, jtv <jtv@xs4all.nl> wrote:

> On Tue, Jan 08, 2002 at 01:27:34AM +0100, J.A. Magallon wrote:
>> >
>> >	int a = 3;
>> >	{
>> >		volatile int b = 10;
>> 
>> >>>>>>>>> here b changes

> Yes, thank you, that part was obvious already.  The question pertained
> to the fact that nobody outside compiler-visible code was being handed
> an address for b, and so the compiler could (if it wanted to) prove
> under pretty broad assumptions that nobody could *find* b to make the
> change in the first place.

How about a debugger?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me



More information about the Gcc mailing list