From: Andrew Pinski <pinskia@gmail.com>
To: dxq <ziyan01@163.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: FRE may run out of memory
Date: Sat, 08 Feb 2014 08:04:00 -0000 [thread overview]
Message-ID: <CA+=Sn1mo6gGyJC=7fYdg_fmxz5h1VkrV7SyQEgrNUdHxDr3sXA@mail.gmail.com> (raw)
In-Reply-To: <1391844590227-1009578.post@n5.nabble.com>
On Fri, Feb 7, 2014 at 11:29 PM, dxq <ziyan01@163.com> wrote:
> hi all,
>
> We found that gcc would run out of memory on Windows when compiling a *big*
> function (100000 lines).
My suggestion to you is file a bug to http://gcc.gnu.org/bugzilla with
the preprocessed source. Also with the exact version of GCC you have
tried. There have been some improvements with the extreme testcases;
at least on the trunk of GCC sources.
Thanks,
Andrew Pinski
>
> More investigation shows that gcc crashes at the function *compute_avail*,
> in tree-fre pass. *compute_avail* collects information from basic blocks,
> so memory is allocated to record informantion.
> However, if there are huge number of basic blocks, the memory would be
> exhausted and gcc would crash down, especially for Windows PC, only 2G or 4G
> memory generally. It's ok On linux, and *compute_avail* allocates *2.4G*
> memory. I guess some optimization passes in gcc like FRE didn't consider the
> extreme
> case.
>
> When disable tree-fre pass, gcc crashes at IRA pass. I will do more
> investigation about that.
>
> Any suggestions?
>
> Thanks!
>
> danxiaoqiang
>
>
>
> --
> View this message in context: http://gcc.1065356.n5.nabble.com/FRE-may-run-out-of-memory-tp1009578.html
> Sent from the gcc - patches mailing list archive at Nabble.com.
parent reply other threads:[~2014-02-08 8:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1391844590227-1009578.post@n5.nabble.com>]
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='CA+=Sn1mo6gGyJC=7fYdg_fmxz5h1VkrV7SyQEgrNUdHxDr3sXA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=ziyan01@163.com \
/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: link
Be 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).