public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/10323: The preprocessor consumes all the memory Date: Mon, 07 Apr 2003 06:46:00 -0000 [thread overview] Message-ID: <20030407064600.898.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/10323; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Neil Booth <neil@daikokuya.co.uk> Cc: lu_zero@gentoo.org, gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/10323: The preprocessor consumes all the memory Date: Sun, 06 Apr 2003 23:36:31 -0700 Neil Booth <neil@daikokuya.co.uk> writes: > Zack Weinberg wrote:- > >> lu_zero@gentoo.org writes: >> >> > Preprocessing altivec code it just consumes all the memory and then >> > dies reporting: >> > cpp0: Cannot allocate 262144112 bytes after allocating 7222368 bytes >> >> I can confirm this with mainline, it looks like infinite recursion in >> the macro expander. Neil, can you take a look? > > I'm pretty certain that the macro expander doesn't recurse or loop. > > I've looked at it briefly. It looks like everything is OK - the expansion > is just 100s of megabytes or even gigabytes big. Oh, ok, I probably just got sick of waiting and ^C-ed it before it finished / ran out of memory. zw
next reply other threads:[~2003-04-07 6:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-07 6:46 Zack Weinberg [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-07 7:15 neil 2003-04-07 6:16 Neil Booth 2003-04-06 23:06 Zack Weinberg 2003-04-06 22:56 Neil Booth 2003-04-06 22:46 Zack Weinberg 2003-04-06 21:26 lu_zero
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=20030407064600.898.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --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).