public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jason@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gwesp@cosy.sbg.ac.at, nobody@gcc.gnu.org Subject: Re: c++/4683: constructor executed at least twice Date: Tue, 09 Apr 2002 09:40:00 -0000 [thread overview] Message-ID: <20020409164014.3067.qmail@sources.redhat.com> (raw) Synopsis: constructor executed at least twice State-Changed-From-To: open->feedback State-Changed-By: jason State-Changed-When: Tue Apr 9 09:40:13 2002 State-Changed-Why: Your bug report doesn't mention actual bad code semantics; the gdb behavior you mention is common for optimized code. It may not be ideal, but it's not a bug either. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4683
next reply other threads:[~2002-04-09 16:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-09 9:40 jason [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-19 4:16 jason 2001-10-25 16:28 Gerhard Wesp
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=20020409164014.3067.qmail@sources.redhat.com \ --to=jason@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gwesp@cosy.sbg.ac.at \ --cc=nobody@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).