diff options
| author | Jason Merrill <jason@redhat.com> | 2021-07-09 05:45:03 -0400 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2021-07-14 14:59:56 -0400 |
| commit | b15e301748f0e042379909e32b3ade439dd8f8f9 (patch) | |
| tree | 16cda41375af0b9e2b0f01c9c8305ac7d4f28f9d /gcc/tree-diagnostic.c | |
| parent | 4940166a15193d6583b320f2957af8720745b76c (diff) | |
| download | gcc-b15e301748f0e042379909e32b3ade439dd8f8f9.zip gcc-b15e301748f0e042379909e32b3ade439dd8f8f9.tar.gz gcc-b15e301748f0e042379909e32b3ade439dd8f8f9.tar.bz2 | |
c++: enable -fdelete-dead-exceptions by default
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.
Diffstat (limited to 'gcc/tree-diagnostic.c')
0 files changed, 0 insertions, 0 deletions