Jakub Jelinek writes: > This is wrong, although you shut up a warning, you actually create > code which (unlike original) does the illegal type punning > (and thus the compiler might/will miscompile it). So you're saying that gcc will warn on code which is actually OK, but won't warn on code that is actually broken? Great. :( Paul.