------- Comment #3 from sabre at nondot dot org 2008-07-25 22:31 -------
Though that does raise a question. Does GCC normally emit errors for undefined
behavior? I thought the policy was to insert runtime traps? If so, doesn't
the { x; } case qualify, or does it violate some other constraint?-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36941
