[Bug c++/114844] New: A trivial but noexcept(false) destructor is incorrectly considered non-throwing

[Bug c++/114844] New: A trivial but noexcept(false) destructor is incorrectly considered non-throwing

[de34 at live dot cn]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114844

            Bug ID: 114844
           Summary: A trivial but noexcept(false) destructor is
                    incorrectly considered non-throwing
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: accepts-invalid, rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: de34 at live dot cn
  Target Milestone: ---

Currently, GCC incorrectly accepts the following code snippet (allowed by
P1286R2), which conflicts with [except.spec]/6.2.

```
struct TrivialButPotentiallyThrowingDestructor {
    TrivialButPotentiallyThrowingDestructor() = default;
    ~TrivialButPotentiallyThrowingDestructor() noexcept(false) = default;
};

static_assert(noexcept(TrivialButPotentiallyThrowingDestructor{}), "???");
```

It's curious that other compilers except for EDG also get this wrong
(https://godbolt.org/z/57jf98xhc).

[Bug c++/114844] A trivial but noexcept(false) destructor is incorrectly considered non-throwing

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114844

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This reminds me of my old patch:
https://gcc.gnu.org/legacy-ml/gcc-patches/2019-09/msg00311.html
this sounds like the problem I hit when working on the patch.