On Thu, Mar 24, 2005 at 09:27:37PM +0000, Joseph S. Myers wrote:
Undefined behavior on execution, not on translation.
It's still a stretch on the word "valid".
It's probably reasonable to say that this is not absolutely a showstopper, as well-written code presumably won't contain this kind of construct.
I suppose one approach would be to decree the C front end broken, and require that it replace the problematic constructs with "abort()", as Joseph mentioned as a possibility. I don't know how tractable that is, but you and Joseph are the C front end maintainers, so you probably do. :-)
-- Mark Mitchell CodeSourcery, LLC [EMAIL PROTECTED] (916) 791-8304
