https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69517
--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Martin Sebor from comment #3) > Just to clarify: it's the program that crashes, not GCC (so removing the > ice-on-invalid-code keyword). > > But I also think that rejecting or at least loudly diagnosing the code would > be preferable to letting it run off the rails. We have tentatively agreed > on this approach in a separate thread > (https://gcc.gnu.org/ml/gcc-patches/2016-01/msg02167.html) so someone just > needs to put together a patch. I'll see if I can find the time to do it if > no one beats me to it. Thanks. > With that said, I wonder if restoring the exception that 4.9.3 would be > feasible. It seems like the ideal solution, in line with the array new > expression. Jason. were there problems with it that the exception throwing > code had to be removed? The only issue was that the exception class was removed from the working paper, so it isn't part of C++14. I'm open to restoring the throwing code, but we should probably use a different exception type, either bad_array_new_length or an extension.
