public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stefan@snon.net Subject: Re: c++/9779: [3.4 regression] ICE in type_unknown_p when casting in static member Date: Thu, 20 Feb 2003 20:15:00 -0000 [thread overview] Message-ID: <20030220201538.5164.qmail@sources.redhat.com> (raw) Old Synopsis: ICE when casting in static member New Synopsis: [3.4 regression] ICE in type_unknown_p when casting in static member State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Thu Feb 20 20:15:38 2003 State-Changed-Why: Confirmed. Here's a smaller snippit: ------------------- void *malloc(unsigned int size); template<int> void foo() { malloc (sizeof (int)); } template void foo<1>(); -------------------------- g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc x.cc: In function `void foo()': x.cc:5: internal compiler error: Segmentation fault This ICEs present mainline, and the regression was introduced between 2002-12-25 and 2003-01-05, i.e. possibly with the new parser. 3.3 is ok. A backtrace shows this: #0 0x08104253 in type_unknown_p (exp=0x4017bf30) at ../../gcc-3.4-CVS/gcc/cp/typeck.c:191 #1 0xbfffeac8 in ?? () #2 0x080e039e in arg_assoc (k=0xbfffeb20, n=0x4018b884) at ../../gcc-3.4-CVS/gcc/cp/decl2.c:4001 #3 0x080e0325 in arg_assoc_args (k=0xbfffeb20, args=0x4018b884) at ../../gcc-3.4-CVS/gcc/cp/decl2.c:3985 #4 0x080e0826 in lookup_arg_dependent (name=0x4015b580, fns=0x401902f4, args=0x0) at ../../gcc-3.4-CVS/gcc/cp/decl2.c:4089 #5 0x080f2825 in cp_parser_postfix_expression (parser=0x40192080, address_p=false) at ../../gcc-3.4-CVS/gcc/cp/parser.c:3948 From there I don't know further, of course. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9779
next reply other threads:[~2003-02-20 20:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 20:15 bangerth [this message] 2003-02-20 20:56 Steven Bosscher
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=20030220201538.5164.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=bkoz@redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=stefan@snon.net \ /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).