'abort: core dumped' is not a good user experience. If code is being
shipped with naked aborts in it, that is where the problem lies.
You're entitled to your opinion, but such a conclusion requires much
stronger basis than this.
If
cross jumping makes debugging harder, tough -- debugging is hard,
debugging optimized programs is harder.
There is no room in software development for responding to a bug
report with "tough". That attitude is incompatible with trying to
serve the users.
Ideally we would satisfy all wishes of all users. That is not
feasible; there are times when we must say no, and for good reason.
But we should never say no when we can easily and painlessly say yes.
(And when we have to say no, we should never say "tough".)
GCC should handle the case of programs using `abort' in the best way
that is reasonably feasible. GCC should handle each and every case in
the most useful way that is reasonably feasible.
This case would not be worth a lot of work. But since we know exactly
what would make it better, and it is a small change, there's no reason
not to do it.
