As I was discussing with richi, I don't think it makes sense to protect
calls to pure/const functions from DCE just because they aren't explicitly
declared noexcept. PR100382 indicates that there are different
considerations for Go, which has non-call exceptions. But still turn the
flag off for that specific testcase.
gcc/c-family/ChangeLog:
* c-opts.c (c_common_post_options): Set -fdelete-dead-exceptions.
gcc/ChangeLog:
* doc/invoke.texi: -fdelete-dead-exceptions is on by default for
C++.
gcc/testsuite/ChangeLog:
* g++.dg/torture/pr100382.C: Pass -fno-delete-dead-exceptions.
SET_OPTION_IF_UNSET (&global_options, &global_options_set, flag_finite_loops,
optimize >= 2 && cxx_dialect >= cxx11);
+ /* It's OK to discard calls to pure/const functions that might throw. */
+ SET_OPTION_IF_UNSET (&global_options, &global_options_set,
+ flag_delete_dead_exceptions, true);
+
if (cxx_dialect >= cxx11)
{
/* If we're allowing C++0x constructs, don't warn about C++98
@opindex fdelete-dead-exceptions
Consider that instructions that may throw exceptions but don't otherwise
contribute to the execution of the program can be optimized away.
-This option is enabled by default for the Ada compiler, as permitted by
-the Ada language specification.
+This does not affect calls to functions except those with the
+@code{pure} or @code{const} attributes.
+This option is enabled by default for the Ada and C++ compilers, as permitted by
+the language specifications.
Optimization passes that cause dead exceptions to be removed are enabled independently at different optimization levels.
@item -funwind-tables
// { dg-do run }
+// { dg-additional-options -fno-delete-dead-exceptions }
int x, y;
int __attribute__((pure,noinline)) foo () { if (x) throw 1; return y; }