public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8564 Date: Thu, 12 Dec 2002 08:06:00 -0000 [thread overview] Message-ID: <20021212160607.13255.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8564; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/8564 Date: Thu, 12 Dec 2002 10:04:47 -0600 (CST) This patchset: > 2001-01-03 Jason Merrill <jason@redhat.com> > > * init.c (build_default_init): New fn. > (perform_member_init): Split out from here. > (build_new_1): Use it. Simplify initialization logic. > (build_vec_init): Take an array, rather than a pointer and maxindex. > Speed up simple initializations. Don't clean up if we're assigning. > * cp-tree.h: Adjust. > * decl2.c (do_static_initialization): Remove TREE_VEC case. > * parse.y (new_initializer): Return void_zero_node for (). > * typeck.c (build_modify_expr): Handle getting a CONSTRUCTOR. > * typeck2.c (digest_init): Only complain about user-written > CONSTRUCTORs. is causing high priority regression PR 8564. The testcase for this PR is ------------------------ struct A { static char* p; }; int i = 1; char* A::p = new char[i]; void foo() {} ------------------------ It fails like so: bash-2.05$ ../gcc/bin-2001-01-02/gcc/cc1plus -O -quiet PR8564.cc PR8564.cc: In function `void __static_initialization_and_destruction_0(int, int)': PR8564.cc:8: Internal compiler error in find_function_data, at function.c:327 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-12-12 16:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-12 8:06 Wolfgang Bangerth [this message] 2003-01-17 3:46 c++/8564 jason 2003-01-17 3:46 c++/8564 jason 2003-01-17 3:46 c++/8564 jason
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=20021212160607.13255.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --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).