https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101882
--- Comment #26 from Segher Boessenkool <segher at gcc dot gnu.org> --- (In reply to chenglulu from comment #25) > > And if the input is non-sensical, the compiler output will be as well, or > > the > > compiler can give up in some cases. > > > I also don't quite agree that this is a user error. If the user's code > follows the C standard, shouldn't the compiler ICE even if the output > doesn't make sense? The stuff we are talking about here never ever follows the C standard of course, it uses many GNU extensions. If a program is wrong, undefined behaviour for example, the compiler cannot always detect that. Not until the halting problem is solved. It is very nice if we can give nicer error messages, but there is a limit to possibility there.
