public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/37722] destructors not called on computed goto Date: Thu, 21 Dec 2023 02:07:21 +0000 [thread overview] Message-ID: <bug-37722-4-1xsugHiWyL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-37722-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37722 --- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:4d9e0f3f211c8c459f285b5cddabc9958ad170f8 commit r14-6765-g4d9e0f3f211c8c459f285b5cddabc9958ad170f8 Author: Jason Merrill <jason@redhat.com> Date: Wed Dec 20 13:58:16 2023 -0500 c++: computed goto warning [PR37722] PR37722 complains that a computed goto doesn't destroy objects that go out of scope. In the PR we agreed that it never will, but we can warn about it. PR c++/37722 gcc/ChangeLog: * doc/extend.texi: Document that computed goto does not call destructors. gcc/cp/ChangeLog: * decl.cc (identify_goto): Adjust for computed goto. (struct named_label_use_entry): Add computed_goto field. (poplevel_named_label_1): Add to computed_goto vec. (check_previous_goto_1): Dump computed_goto vec. (check_goto_1): Split out from check_goto. (check_goto): Check all addressable labels for computed goto. (struct named_label_entry): Add addressed field. (mark_label_addressed): New. * parser.cc (cp_parser_unary_expression): Call it. * cp-tree.h (mark_label_addressed): Declare it. gcc/testsuite/ChangeLog: * g++.dg/ext/label15.C: New test. * g++.dg/torture/pr42739.C: Expect warning.
next prev parent reply other threads:[~2023-12-21 2:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-37722-4@http.gcc.gnu.org/bugzilla/> 2013-01-11 14:52 ` timo.kreuzer at reactos dot org 2022-01-03 12:00 ` pinskia at gcc dot gnu.org 2022-01-03 17:33 ` jakub at gcc dot gnu.org 2023-07-19 16:46 ` ndesaulniers at google dot com 2023-12-21 2:07 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-21 2:08 ` jason at gcc dot gnu.org 2024-01-03 4:23 ` egallager at gcc dot gnu.org 2008-10-02 20:46 [Bug c++/37722] New: " cburger at sunysb dot edu 2008-10-02 21:23 ` [Bug middle-end/37722] " pinskia at gcc dot gnu dot org 2009-05-09 8:17 ` scovich at gmail dot com
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-37722-4-1xsugHiWyL@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).