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 ipa/62016] [4.8/4.9 Regression] very slow compilation at -O3 on x86_64-linux-gnu
Date: Fri, 16 Jan 2015 09:34:00 -0000	[thread overview]
Message-ID: <bug-62016-4-JbDsSkfesd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62016-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62016

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |5.0
            Summary|[4.8/4.9/5 Regression] very |[4.8/4.9 Regression] very
                   |slow compilation at -O3 on  |slow compilation at -O3 on
                   |x86_64-linux-gnu            |x86_64-linux-gnu
      Known to fail|                            |4.8.3, 4.9.2

--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yep.

> /usr/bin/time gcc-4.7 t.c -O3
0.10user 0.02system 0:00.62elapsed 21%CPU (0avgtext+0avgdata 15704maxresident)k
26080inputs+48outputs (113major+9177minor)pagefaults 0swaps
> /usr/bin/time gcc-4.8 t.c -O3
^C
0.00user 0.00system 6:11.40elapsed 0%CPU (0avgtext+0avgdata 1136maxresident)k
1440inputs+0outputs (7major+331minor)pagefaults 0swaps
> /usr/bin/time gcc-4.9 t.c -O3
3.13user 0.18system 0:03.84elapsed 86%CPU (0avgtext+0avgdata
404088maxresident)k
28400inputs+48outputs (128major+137978minor)pagefaults 0swaps
> /usr/bin/time /space/rguenther/install/gcc-5.0/bin/gcc t.c -O3
0.04user 0.01system 0:00.28elapsed 20%CPU (0avgtext+0avgdata 13364maxresident)k
6376inputs+48outputs (17major+8570minor)pagefaults 0swaps


  parent reply	other threads:[~2015-01-16  9:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  5:12 [Bug ipa/62016] New: " su at cs dot ucdavis.edu
2014-08-05  9:07 ` [Bug ipa/62016] [4.8/4.9/4.10 Regression] " rguenth at gcc dot gnu.org
2014-08-05  9:08 ` rguenth at gcc dot gnu.org
2014-08-05  9:11 ` trippels at gcc dot gnu.org
2014-08-07 20:50 ` hubicka at gcc dot gnu.org
2014-08-11  9:10 ` jakub at gcc dot gnu.org
2014-08-11 10:44 ` jakub at gcc dot gnu.org
2014-11-24 13:04 ` [Bug ipa/62016] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` jakub at gcc dot gnu.org
2014-12-19 21:19 ` hubicka at gcc dot gnu.org
2015-01-16  7:19 ` hubicka at gcc dot gnu.org
2015-01-16  9:34 ` rguenth at gcc dot gnu.org [this message]
2015-06-23  8:19 ` [Bug ipa/62016] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-06-26 19:56 ` [Bug ipa/62016] [4.9 " jakub at gcc dot gnu.org
2015-06-26 20:28 ` 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-62016-4-JbDsSkfesd@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).