public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "evgeniya.maenkova at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54488] tree loop invariant motion uses an excessive amount of memory
Date: Fri, 10 Oct 2014 13:34:00 -0000 [thread overview]
Message-ID: <bug-54488-4-gc7Gm9mBdC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54488-4@http.gcc.gnu.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.
next prev parent reply other threads:[~2014-10-10 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 10:21 [Bug tree-optimization/54488] New: " rguenth at gcc dot gnu.org
2014-10-10 13:34 ` evgeniya.maenkova at gmail dot com [this message]
2014-10-19 16:02 ` [Bug tree-optimization/54488] " evgeniya.maenkova at gmail dot com
2014-10-19 19:43 ` evgeniya.maenkova at gmail dot com
2014-10-20 13:38 ` evgeniya.maenkova at gmail dot com
2014-10-21 9:24 ` rguenth at gcc dot gnu.org
2014-10-21 11:15 ` evgeniya.maenkova at gmail dot 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=bug-54488-4-gc7Gm9mBdC@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: 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).