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/53852] [4.8 Regression] -ftree-loop-linear: large compile time / memory usage
Date: Wed, 04 Jul 2012 12:44:00 -0000 [thread overview]
Message-ID: <bug-53852-4-DDsYaHafHb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53852-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53852
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |tree-optimization
Known to work| |4.7.1
Target Milestone|--- |4.8.0
Summary|-ftree-loop-linear: large |[4.8 Regression]
|compile time / memory usage |-ftree-loop-linear: large
| |compile time / memory usage
--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-04 12:43:48 UTC ---
4.7 compiles this quickly and without too much memory.
next prev parent reply other threads:[~2012-07-04 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 11:19 [Bug middle-end/53852] New: " Joost.VandeVondele at mat dot ethz.ch
2012-07-04 11:54 ` [Bug middle-end/53852] " rguenth at gcc dot gnu.org
2012-07-04 12:11 ` matz at gcc dot gnu.org
2012-07-04 12:18 ` Joost.VandeVondele at mat dot ethz.ch
2012-07-04 12:44 ` rguenth at gcc dot gnu.org [this message]
2012-08-22 11:58 ` [Bug tree-optimization/53852] [4.8 Regression] " Joost.VandeVondele at mat dot ethz.ch
2012-12-06 16:25 ` rguenth at gcc dot gnu.org
2012-12-13 13:00 ` rguenth at gcc dot gnu.org
2013-02-07 9:05 ` Joost.VandeVondele at mat dot ethz.ch
2013-02-19 20:48 ` law at redhat dot com
2013-03-22 14:43 ` [Bug tree-optimization/53852] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:58 ` jakub at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2014-01-23 7:30 ` law at redhat dot com
2014-05-22 9:02 ` [Bug tree-optimization/53852] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:41 ` [Bug tree-optimization/53852] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:23 ` [Bug tree-optimization/53852] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:13 ` [Bug tree-optimization/53852] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:37 ` jakub at gcc dot gnu.org
2015-08-28 4:28 ` Joost.VandeVondele at mat dot ethz.ch
2015-08-28 14:29 ` spop at gcc dot gnu.org
2015-09-02 22:38 ` spop at gcc dot gnu.org
2015-09-09 4:23 ` spop 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-53852-4-DDsYaHafHb@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).