public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: andreas@florath.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, nobody@gcc.gnu.org Subject: Re: c++/10060: ICE on huge file (300k lines) Date: Mon, 05 May 2003 10:52:00 -0000 [thread overview] Message-ID: <20030505105203.4306.qmail@sources.redhat.com> (raw) Synopsis: ICE on huge file (300k lines) State-Changed-From-To: open->feedback State-Changed-By: bajo State-Changed-When: Mon May 5 10:52:02 2003 State-Changed-Why: Hello Andreas, I have troubles reproducing this because it either hits virtual memory exhausted or compiles correctly, depends on how many objects I make it generate. Would you please confirm that this is still a bug in GCC 3.3 or 3.4, and provide a minimal number of objects that must be generated to trigger it? It seems that compilation time grows O(n^2), so putting a big number means hours of compilation (assuming infinite memory). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10060
next reply other threads:[~2003-05-05 10:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-05 10:52 giovannibajo [this message] 2003-05-09 13:06 andreas 2003-05-09 13:06 Andrew Pinski 2003-05-09 13:16 Giovanni Bajo 2003-05-09 16:36 Andrew Pinski
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=20030505105203.4306.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=andreas@florath.net \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --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).