http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53323
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2013-03-23 12:41:46 UTC --- > ... or have a compiler generate incorrect code. (NB, in this case I accept > that > it may well be the check that's wrong, not the generated code). Yes, that's the key point, there are enough internal assertions in the back-end (which are always enabled) to rule out wrong code generation issues. See: http://gcc.gnu.org/ml/gcc-patches/2013-01/msg00581.html
