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/58957] [4.8 Regression] compilation slow at -O3 on x86_64-linux-gnu (both 32-bit and 64-bit modes)
Date: Mon, 04 Nov 2013 14:36:00 -0000 [thread overview]
Message-ID: <bug-58957-4-EiQS8LqNmp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58957-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58957
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog
Known to work| |4.7.3, 4.9.0
Summary|[4.8 Regression] |[4.8 Regression]
|compilation hangs at -O3 on |compilation slow at -O3 on
|x86_64-linux-gnu (both |x86_64-linux-gnu (both
|32-bit and 64-bit modes) |32-bit and 64-bit modes)
Known to fail| |4.8.0, 4.8.2
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think it's just awfully slow (deep loop nest, possible to unroll completely).
It terminates for me on the branch and for 4.8.2 and 4.8.1.
tree CFG cleanup : 8.49 (88%) usr 0.00 ( 0%) sys 8.52 (87%) wall
783 kB ( 2%) ggc
TOTAL : 9.70 0.06 9.80
51528 kB
on trunk and 4.7.3:
TOTAL : 0.09 0.00 0.10
1865 kB
next prev parent reply other threads:[~2013-11-04 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 5:25 [Bug tree-optimization/58957] New: compilation hangs " su at cs dot ucdavis.edu
2013-11-04 14:36 ` rguenth at gcc dot gnu.org [this message]
2013-11-04 23:21 ` [Bug tree-optimization/58957] [4.8 Regression] compilation slow " su at cs dot ucdavis.edu
2014-12-10 12:48 ` rguenth at gcc dot gnu.org
2014-12-19 13:42 ` jakub at gcc dot gnu.org
2015-06-23 8:46 ` 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-58957-4-EiQS8LqNmp@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).