public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54627] New: VRP uses lots of memory and compile-time
Date: Wed, 19 Sep 2012 14:24:00 -0000	[thread overview]
Message-ID: <bug-54627-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54627

             Bug #: 54627
           Summary: VRP uses lots of memory and compile-time
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: compile-time-hog, memory-hog
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org


Part of it is due to equivalence set bitmaps becoming huge (and their
inefficient computation).  equivalences are only used when trying to
simplify comparisons (but during iteration).  So the only used
equivalence bitmaps are for operands of those.  equivalences are
generated only by asserts and SSA name copies, so they can be computed
up-front and shouldn't change (apart from handling of non-executable
edges in PHI nodes) during iteration.  At least equivalence processing
can be ignored for SSA name chains not leading up to a condition operand.


             reply	other threads:[~2012-09-19 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 14:24 rguenth at gcc dot gnu.org [this message]
2012-10-01 20:41 ` [Bug tree-optimization/54627] " steven at gcc dot gnu.org
2013-03-18  9:49 ` steven at gcc dot gnu.org
2013-03-18 10:04 ` rguenth at gcc dot gnu.org
2023-05-04  5:48 ` aldyh at gcc dot gnu.org
2023-05-04  9:29 ` rguenth at gcc dot gnu.org

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-54627-4@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).