public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13215] [3.3 Regression] bad code generated to call operator new[] when -fcheck-new Date: Mon, 22 Dec 2003 05:33:00 -0000 [thread overview] Message-ID: <20031222052551.18053.qmail@sources.redhat.com> (raw) In-Reply-To: <20031128115140.13215.tom@storagematrix.com> ------- Additional Comments From mmitchel at gcc dot gnu dot org 2003-12-22 05:25 ------- It's not practical to backport the mainline changes to GCC 3.3.3. I don't think that it's worth spending effort to fix this bug for GCC 3.3.3, so I've removed my name from the assigned field. However, if I caused this regression and Gaby thinks it's imperative that this bug be fixed, I will see if I can fix the problem. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mmitchel at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|ASSIGNED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13215
next prev parent reply other threads:[~2003-12-22 5:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-28 11:51 [Bug c++/13215] New: " tom at storagematrix dot com 2003-11-28 13:14 ` [Bug c++/13215] " falk at debian dot org 2003-11-28 17:34 ` [Bug c++/13215] [3.3 only] " pinskia at gcc dot gnu dot org 2003-12-01 2:06 ` [Bug c++/13215] [3.3 Regression] " pinskia at gcc dot gnu dot org 2003-12-21 21:47 ` pinskia at gcc dot gnu dot org 2003-12-21 21:47 ` pinskia at gcc dot gnu dot org 2003-12-21 21:52 ` pinskia at gcc dot gnu dot org 2003-12-22 5:33 ` mmitchel at gcc dot gnu dot org [this message] 2003-12-22 5:46 ` gdr at integrable-solutions dot net 2003-12-22 22:57 ` pinskia at gcc dot gnu dot org 2005-02-15 22:22 ` pinskia 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=20031222052551.18053.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).