public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/106898] New: ECF_NOTHROW for __cxa_deleted_virtual or not for __cxa_pure_virtual
@ 2022-09-10  2:45 aoliva at gcc dot gnu.org
  0 siblings, 0 replies; only message in thread
From: aoliva at gcc dot gnu.org @ 2022-09-10  2:45 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 106898
           Summary: ECF_NOTHROW for __cxa_deleted_virtual or not for
                    __cxa_pure_virtual
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: aoliva at gcc dot gnu.org
  Target Milestone: ---

I see no reason for the difference WRT ECF_NOTHROW between
__cxa_deleted_virtual and __cxa_pure_virtual library declarations pushed in
decl.cc and class.cc, respectively.  Their implementations behave essentially
the same, I suppose both might be user-overridable (though I see no evidence
that this is indeed the case), and neither promises not to throw in the C++ ABI
document (but I realize throwing from either one could be problematic if the
virtual method happens to be nothrow).

Unless there's good reason to keep this flag difference, IMHO it would be
desirable to resolve the inconsistency one way or another.

^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2022-09-10  2:45 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-10  2:45 [Bug c++/106898] New: ECF_NOTHROW for __cxa_deleted_virtual or not for __cxa_pure_virtual aoliva at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).