public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14724] [3.3/3.4/3.5 Regression] Destructor not called on backwards goto past initialization Date: Fri, 26 Mar 2004 01:40:00 -0000 [thread overview] Message-ID: <20040326014028.25214.qmail@sources.redhat.com> (raw) In-Reply-To: <20040324223333.14724.gson@gson.org> ------- Additional Comments From giovannibajo at libero dot it 2004-03-26 01:40 ------- For the logs, I can reproduce it with: gcc version 3.3.4 20040218 (prerelease) gcc version 3.4.0 20040216 (prerelease) gcc version 3.2.2 (mingw special 20030208-1) on i686-cygwin. Andrew Pinski can reproduce it with: gcc version 3.5.0 20040325 (experimental) on i686-linux and powerpc-apple-darwin. But RTH couldn't reproduce it with gcc version 3.3.3 (Debian) on alpha, or mainline on linux. So there must be something weird going on. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14724
next prev parent reply other threads:[~2004-03-26 1:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-24 22:33 [Bug c++/14724] New: " gson at gson dot org 2004-03-24 23:00 ` [Bug c++/14724] " bangerth at dealii dot org 2004-03-25 1:25 ` [Bug c++/14724] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-03-26 1:40 ` giovannibajo at libero dot it [this message] 2004-03-26 15:14 ` bangerth at dealii dot org 2004-03-30 22:19 ` mmitchel at gcc dot gnu dot org 2004-03-30 23:43 ` cvs-commit at gcc dot gnu dot org 2004-03-30 23:45 ` cvs-commit at gcc dot gnu dot org 2004-03-30 23:47 ` [Bug c++/14724] [3.3 " mmitchel at gcc dot gnu dot org 2004-04-13 21:35 ` cvs-commit at gcc dot gnu dot org 2004-05-01 19:57 ` cvs-commit at gcc dot gnu dot org 2004-05-01 19:58 ` gdr at gcc dot gnu dot 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=20040326014028.25214.qmail@sources.redhat.com \ --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).