public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/14711] [3.3 regression] ICE in final.c:2117 when compiling a huge source file Date: Wed, 24 Mar 2004 16:51:00 -0000 [thread overview] Message-ID: <20040324165122.7420.qmail@sources.redhat.com> (raw) In-Reply-To: <20040324065726.14711.debian-gcc@lists.debian.org> ------- Additional Comments From reichelt at gcc dot gnu dot org 2004-03-24 16:51 ------- Looks like Falk is right, I'll attach a short testcase which has the following form: ============================ template <int> struct A {}; // lots of empty lines void foo() { A<0> a; } ============================ If the funtion is in line 524288, I get the ICE, if it is in line 524287 I don't. -- What |Removed |Added ---------------------------------------------------------------------------- CC| |reichelt at gcc dot gnu dot | |org Severity|normal |critical Status|WAITING |NEW Component|preprocessor |middle-end Ever Confirmed| |1 Known to fail| |3.3 3.3.1 3.3.2 3.3.3 Known to work| |2.95.3 3.4.0 3.5.0 Last reconfirmed|0000-00-00 00:00:00 |2004-03-24 16:51:21 date| | Summary|ICE in final.c:2117 when |[3.3 regression] ICE in |compiling a huge source file|final.c:2117 when compiling | |a huge source file Target Milestone|--- |3.3.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14711
next prev parent reply other threads:[~2004-03-24 16:51 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-24 6:57 [Bug c++/14711] New: " debian-gcc at lists dot debian dot org 2004-03-24 13:57 ` [Bug c++/14711] " giovannibajo at libero dot it 2004-03-24 15:42 ` bangerth at dealii dot org 2004-03-24 16:24 ` falk at debian dot org 2004-03-24 16:27 ` [Bug middle-end/14711] " pinskia at gcc dot gnu dot org 2004-03-24 16:50 ` [Bug preprocessor/14711] " pinskia at gcc dot gnu dot org 2004-03-24 16:51 ` reichelt at gcc dot gnu dot org [this message] 2004-03-24 16:53 ` [Bug middle-end/14711] [3.3 regression] " gdr at integrable-solutions dot net 2004-03-24 17:06 ` bangerth at dealii dot org 2004-03-24 17:08 ` reichelt at gcc dot gnu dot org 2004-03-24 17:09 ` giovannibajo at libero dot it 2004-03-24 17:44 ` reichelt at gcc dot gnu dot org 2004-03-24 17:47 ` bangerth at dealii dot org 2004-04-04 20:54 ` roger at eyesopen dot com 2004-04-06 16:40 ` jsm at polyomino dot org dot uk 2004-04-15 15:45 ` reichelt at gcc dot gnu dot org 2004-04-18 19:44 ` gdr at gcc dot gnu dot org 2004-05-15 17:19 ` bangerth at dealii dot org 2004-05-15 20:39 ` [Bug middle-end/14711] [3.3/3.4/3.5 " pinskia at gcc dot gnu dot org 2004-06-19 0:02 ` mmitchel at gcc dot gnu dot org 2004-08-29 18:16 ` mmitchel at gcc dot gnu dot org 2004-08-29 18:16 ` mmitchel at gcc dot gnu dot org 2004-11-01 0:45 ` [Bug middle-end/14711] [3.3/3.4/4.0 " mmitchel at gcc dot gnu dot org 2004-12-05 20:20 ` pinskia at gcc dot gnu dot org 2004-12-06 4:53 ` pinskia at gcc dot gnu dot org 2005-03-24 18:15 ` [Bug middle-end/14711] [3.3/3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-03-24 20:35 ` [Bug middle-end/14711] [3.3/3.4 " reichelt at gcc dot gnu dot org 2005-05-10 1:39 ` mmitchel 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=20040324165122.7420.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).