Volatile MEMs in statement expressions and functions inlined as trees

[Alexandre Oliva]

On Dec 14, 2001, Linus Torvalds <torvalds@transmeta.com> wrote:

> 	int c;

> 	(char) c;

> then that expression _is_ in fact an lvalue (in gcc, not in C in general),

Hmm...  So, if I have:

  volatile int c;

  (volatile char)c;

Do I read a char or an int from c's address?

Does it matter if one of the `volatile's is ommitted?

And now, an easy question: is this yet another GCC extension whose
consequences were not fully thought-out in advance? :-)

-- 
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