https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70076
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=70652
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #6)
> The current behavior in this case is undefined. That should be avoided when
> it can be done without excessive overhead. Throwing an exception instead
> has only negligible overhead and is preferable to letting programs trash
> their stack. The original patch that did that was approved and committed
> but caused a linker error while building libgcj.so due to its own problems
> (pr70652). Because it was too close to GCC 6 release it ended up getting
> reverted instead of fixing libgcj. I've been meaning to resubmit the patch
> for each release after that but I never seem to get around to it. Hopefully
> for GCC 10.
Well since libgcj is no longer part of GCC, that part should no longer be an
issue at least!
