This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/54488] tree loop invariant motion uses an excessive amount of memory
- From: "evgeniya.maenkova at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 10 Oct 2014 13:34:03 +0000
- Subject: [Bug tree-optimization/54488] tree loop invariant motion uses an excessive amount of memory
- Auto-submitted: auto-generated
- References: <bug-54488-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54488
Evgeniya Maenkova <evgeniya.maenkova at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |evgeniya.maenkova at gmail dot com
--- Comment #1 from Evgeniya Maenkova <evgeniya.maenkova at gmail dot com> ---
Could you please clarify this bug status? (As I can see PR46590 you applied
some patch that fixes memory issues in Jan of 2014).
As I can see from the code (I'm very newbie, sorry for mistakes) there are the
structures which keep the information about memory accesses in the whole
function (for all the loops).
When I read you comment in this bug I started to think there is some
possibility to keep the only information about individual loop (which I could
try to implement). However, the comment in PR46590 says you meant something
different.