public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114357] Add a way to not call deconstructors for non-auto decls, like clang's no_destroy attribute Date: Fri, 15 Mar 2024 22:02:30 +0000 [thread overview] Message-ID: <bug-114357-4-ASZRt35nzO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114357-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114357 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Summary|C++: Support the no_destroy |Add a way to not call |attribute |deconstructors for non-auto | |decls, like clang's | |no_destroy attribute --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Really having this attribute to work around broken C++ code is just asking for more troubles. There was a request recently for asking to remove the store for the vtable in trivial deconstructors to work around broken C++ code and it was obvious that the developer didn't know how it was broken and just wanted to this attribute to workaround their broken code.
next prev parent reply other threads:[~2024-03-15 22:02 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-15 21:48 [Bug c++/114357] New: C++: Support the " i at maskray dot me 2024-03-15 21:59 ` [Bug c++/114357] " pinskia at gcc dot gnu.org 2024-03-15 22:02 ` pinskia at gcc dot gnu.org [this message] 2024-03-15 22:08 ` [Bug c++/114357] Add a way to not call deconstructors for non-auto decls, like clang's " jfb at chromium dot org 2024-03-15 22:09 ` pinskia at gcc dot gnu.org 2024-03-15 22:25 ` jfb at chromium dot org 2024-03-15 22:26 ` pinskia at gcc dot gnu.org 2024-03-15 23:46 ` redi at gcc dot gnu.org 2024-03-16 10:35 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-114357-4-ASZRt35nzO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).