public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/18369] [4.0 regression] Segfault on braced new Date: Thu, 06 Jan 2005 00:20:00 -0000 [thread overview] Message-ID: <20050106002051.14473.qmail@sourceware.org> (raw) In-Reply-To: <20041108065030.18369.mueller@kde.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-06 00:20 ------- Subject: Bug 18369 CVSROOT: /cvs/gcc Module name: gcc Branch: apple-ppc-branch Changes by: austern@gcc.gnu.org 2005-01-06 00:20:31 Modified files: gcc/cp : ChangeLog.apple-ppc init.c gcc/testsuite : ChangeLog.apple-ppc Added files: gcc/testsuite/g++.dg/init: new12.C Log message: radar 3934803 PR c++/18369 * init.c (build_new_1): Handle parenthesized type-ids that name an array type. Tidy. * g++.dg/init/new12.C: New test. - Customer impact (why this needs to be fixed): This bug causes the compiler to crash whenever it encounters a certain construct that's moderately obscure but only moderately. I expect many large C++ projects to use this construct in at least one place. Among the projects that use this is QuickTimeStreaming, so this radar causes a side world build failure. - Code reviewed by (name): Mark Mitchell for fsf mainline (11/9/04), Geoff Keating for apple-ppc-branch (1/5/05) - Code review date: see above - Root build number the fix was tested in: n/a - Root build date:n/a - What did you do to test the fix: bootstrapped the compiler, ran dg, verified that the new test case that's part of the patch (new12.C) passes, verified that the test case in this radar passes, verified that this patch caused no dg regressions - Is there a test case for this fix? If not, why: yes, see above - Other components affected by this fix (i.e., identify integration points): none - Other groups affected by the fix (i.e., QA, Pubs, other eng groups): QA will have to test it - Is there Localization impact? no - Risk assessment: Low. This patch has been in fsf mainline for the last two months, and nobody has seen a problem with it. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.apple-ppc.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.1.2.22&r2=1.1.2.23 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/init.c.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.281.2.40.2.11&r2=1.281.2.40.2.12 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.apple-ppc.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=1.1.2.72&r2=1.1.2.73 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/init/new12.C.diff?cvsroot=gcc&only_with_tag=apple-ppc-branch&r1=NONE&r2=1.1.14.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18369
prev parent reply other threads:[~2005-01-06 0:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-08 6:50 [Bug c++/18369] New: " mueller at kde dot org 2004-11-08 6:51 ` [Bug c++/18369] " mueller at kde dot org 2004-11-08 10:44 ` reichelt at gcc dot gnu dot org 2004-11-08 12:33 ` pinskia at gcc dot gnu dot org 2004-11-08 13:46 ` pinskia at gcc dot gnu dot org 2004-11-09 6:58 ` mmitchel at gcc dot gnu dot org 2004-11-10 17:01 ` cvs-commit at gcc dot gnu dot org 2004-11-10 17:20 ` mmitchel at gcc dot gnu dot org 2005-01-06 0:20 ` cvs-commit at gcc dot gnu dot org [this message]
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=20050106002051.14473.qmail@sourceware.org \ --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).