This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/51389] GCC uses up to 75GB of virtual memory
- From: "abel at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 24 Jan 2012 09:07:20 +0000
- Subject: [Bug middle-end/51389] GCC uses up to 75GB of virtual memory
- Auto-submitted: auto-generated
- References: <bug-51389-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51389
Andrey Belevantsev <abel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-01-24
CC| |abel at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #2 from Andrey Belevantsev <abel at gcc dot gnu.org> 2012-01-24 09:07:20 UTC ---
Confirmed. We have a loop with a couple thousands of bbs and >20k datarefs,
and we die in a quadratic loops in compute_all_dependences. Can be easily
fixed with a PARAM limiting the data ref analysis.
While doing this, I noticed that there is no reason for
find_data_references_in_loop to be extern and made it static. Also predcom and
parloops are not ready for compute_data_dependences_for_loop returning false,
so I fixed this as well.