------- Comment #2 from rguenth at gcc dot gnu dot org 2008-11-23 12:17 -------
GCC 4.3 is "safe" because it doesn't fall back to anything for p, but uses
{ x, y, ANYTHING } instead. In turn it heavily relies on correct call clobbers
if you obfuscate the pointers. Which makes me not entirely convinced that
I cannot make this latent problem trigger on the 4.3 branch ...
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |4.3.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38236
