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 rtl-optimization/59811] [4.8/4.9 Regression] Huge increase in memory usage and compile time with gfortran 4.8
Date: Wed, 15 Jan 2014 12:06:00 -0000 [thread overview]
Message-ID: <bug-59811-4-lRSU9nUI3F@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59811-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59811
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |4.7.3
Keywords| |compile-time-hog
Last reconfirmed| |2014-01-15
Component|fortran |rtl-optimization
Ever confirmed|0 |1
Summary|Huge increase in memory |[4.8/4.9 Regression] Huge
|usage and compile time with |increase in memory usage
|gfortran 4.8 |and compile time with
| |gfortran 4.8
Target Milestone|--- |4.8.3
Known to fail| |4.8.2, 4.9.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. At -O2 I see for 4.8
alias stmt walking : 4.90 ( 8%) usr 0.02 ( 3%) sys 5.05 ( 8%) wall
0 kB ( 0%) ggc
tree copy propagation : 0.02 ( 0%) usr 0.00 ( 0%) sys 0.02 ( 0%) wall
513 kB ( 0%) ggc
combiner : 45.94 (71%) usr 0.57 (83%) sys 46.57 (71%) wall
1612812 kB (96%) ggc
integrated RA : 0.59 ( 1%) usr 0.01 ( 1%) sys 0.58 ( 1%) wall
12481 kB ( 1%) ggc
LRA hard reg assignment : 7.53 (12%) usr 0.03 ( 4%) sys 7.56 (11%) wall
0 kB ( 0%) ggc
TOTAL : 65.03 0.69 65.92
1681500 kB
and for 4.7
alias stmt walking : 2.77 (28%) usr 0.02 (17%) sys 2.80 (28%) wall
0 kB ( 0%) ggc
tree copy propagation : 1.64 (17%) usr 0.01 ( 8%) sys 1.67 (17%) wall
513 kB ( 1%) ggc
integrated RA : 0.66 ( 7%) usr 0.02 (17%) sys 0.68 ( 7%) wall
6295 kB (10%) ggc
reload : 0.45 ( 5%) usr 0.01 ( 8%) sys 0.46 ( 5%) wall
1593 kB ( 3%) ggc
reload CSE regs : 0.74 ( 7%) usr 0.00 ( 0%) sys 0.75 ( 7%) wall
1103 kB ( 2%) ggc
TOTAL : 9.87 0.12 10.01
61922 kB
the combiner slowdown and the LRA thing are worth investigating. I suppose
the generated code differs quite a bit ;) It's a very large function
with some very large basic-block(s). Current trunk behaves comparable
to GCC 4.8.
next prev parent reply other threads:[~2014-01-15 12:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 17:30 [Bug fortran/59811] New: " bastian.feigl at kit dot edu
2014-01-15 12:06 ` rguenth at gcc dot gnu.org [this message]
2014-01-15 13:53 ` [Bug rtl-optimization/59811] [4.8/4.9 Regression] Huge increase in memory usage and compile time in combine rguenth at gcc dot gnu.org
2014-01-22 15:01 ` jakub at gcc dot gnu.org
2014-01-22 15:16 ` jakub at gcc dot gnu.org
2014-01-31 11:35 ` rguenth at gcc dot gnu.org
2014-01-31 11:41 ` jakub at gcc dot gnu.org
2014-01-31 11:48 ` rguenther at suse dot de
2014-05-22 9:02 ` [Bug rtl-optimization/59811] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:29 ` [Bug rtl-optimization/59811] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:23 ` [Bug rtl-optimization/59811] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:59 ` [Bug rtl-optimization/59811] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub 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-59811-4-lRSU9nUI3F@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).