public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cburger at sunysb dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/37722] New: destructors not called on computed goto Date: Thu, 02 Oct 2008 20:46:00 -0000 [thread overview] Message-ID: <bug-37722-2032@http.gcc.gnu.org/bugzilla/> (raw) #include <iostream> struct foo { foo() { std::cout << "foo constructed\n"; } ~foo() { std::cout << "foo destructed\n"; } }; enum opcode { NOP, FOO, DONE }; void exec0(const opcode* o) { loop: switch (*o) { case NOP: ++o; goto loop; case FOO: { foo f; ++o; goto loop; } // f destructed case DONE: return; } } void exec1(const opcode* o) { static void* label[] = { &&NOP, &&FOO, &&DONE }; goto *label[*o]; NOP: ++o; goto *label[*o]; FOO: { foo f; ++o; goto *label[*o]; } // f not destructed // FOO: { foo f; ++o; } goto *label[*o]; // work-around DONE: return; } int main() { const opcode program[] = { NOP, FOO, NOP, NOP, DONE }; exec0(program); exec1(program); return 0; } Output: foo constructed foo destructed foo constructed Tested with: 4.3.2, 4.2.4, 4.1.3, 3.4.6 Optimization level makes no difference. Intel icpc 10.1, 9.1 show the same problem. -- Summary: destructors not called on computed goto Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: cburger at sunysb dot edu GCC build triplet: x86_64-linux-gnu GCC host triplet: x86_64-linux-gnu GCC target triplet: x86_64-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37722
next reply other threads:[~2008-10-02 20:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-02 20:46 cburger at sunysb dot edu [this message] 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-2032@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).