public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9779: [3.4 regression] ICE in type_unknown_p when casting in static member Date: Thu, 20 Feb 2003 20:56:00 -0000 [thread overview] Message-ID: <20030220205600.4552.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9779; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: bkoz@redhat.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, stefan@snon.net Cc: Subject: Re: c++/9779: [3.4 regression] ICE in type_unknown_p when casting in static member Date: Thu, 20 Feb 2003 21:51:23 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9779 devphil says: : Search converges between 2002-12-27-trunk (#85) and 2002-12-28-trunk (#86). Line-numbered input is: ======================================== 1 void *malloc(unsigned int size); 2 template<int> void foo() { 3 malloc (sizeof (int)); 4 } 5 template void foo<1>(); 6 ======================================== Diagnostic output follows, from the last compiler tested: input: In function `void foo()': input:3: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. Compiler output follows, from the last compiler tested: .file "input" So, 99% sure that this is caused by the new parser. Greetz Steven
next reply other threads:[~2003-02-20 20:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 20:56 Steven Bosscher [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-20 20:15 bangerth
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=20030220205600.4552.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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).