public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/36262] [4.3/4.4 Regression] Extreme memory usage of VRP compared to older versions Date: Tue, 20 May 2008 13:01:00 -0000 [thread overview] Message-ID: <20080520130042.27324.qmail@sourceware.org> (raw) In-Reply-To: <bug-36262-1532@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2008-05-20 13:00 ------- It is not safe. Probably the best thing would be to not ask SCEV during the propagation but instead at ASSERT_EXPR insertion time. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36262
next prev parent reply other threads:[~2008-05-20 13:01 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-18 23:06 [Bug c/36262] New: Extreme memory usage " hakonrk at fys dot uio dot no 2008-05-18 23:07 ` [Bug c/36262] " hakonrk at fys dot uio dot no 2008-05-19 9:19 ` [Bug middle-end/36262] [4.3/4.4 Regression] Extreme memory usage of VRP " rguenth at gcc dot gnu dot org 2008-05-19 9:43 ` rguenth at gcc dot gnu dot org 2008-05-19 11:01 ` rguenth at gcc dot gnu dot org 2008-05-20 13:01 ` rguenth at gcc dot gnu dot org [this message] 2008-05-27 8:32 ` rguenth at gcc dot gnu dot org 2008-05-28 22:09 ` rguenth at gcc dot gnu dot org 2008-05-31 13:02 ` [Bug middle-end/36262] [4.3 " rguenth at gcc dot gnu dot org 2008-05-31 13:02 ` rguenth at gcc dot gnu dot org 2008-06-06 15:05 ` rguenth at gcc dot gnu dot org 2008-06-06 20:07 ` rguenth at gcc dot gnu dot org 2008-06-06 20:08 ` rguenth at gcc dot gnu dot org 2008-07-06 10:00 ` steven at gcc dot gnu dot org 2008-07-06 12:28 ` rguenth at gcc dot gnu dot 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=20080520130042.27324.qmail@sourceware.org \ --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: linkBe 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).