public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time
Date: Thu, 02 Feb 2012 17:36:00 -0000 [thread overview]
Message-ID: <bug-45364-4-XlacBISnOM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45364-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45364
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-02
Host|i686-pc-linux-gnu |
Ever Confirmed|0 |1
Build|i686-pc-linux-gnu |
Severity|enhancement |minor
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-02 17:35:42 UTC ---
With checking still enabled we get:
-O1 -g:
var-tracking dataflow : 7.73 (57%) usr 0.05 (12%) sys 7.78 (56%) wall
0 kB ( 0%) ggc
-O2 -g:
var-tracking dataflow : 15.23 (45%) usr 0.07 (13%) sys 15.33 (45%) wall
0 kB ( 0%) ggc
-O2:
CPROP : 4.35 (27%) usr 0.02 ( 4%) sys 4.36 (27%) wall
2486 kB ( 3%) ggc
on the trunk.
I have not checked without checking enabled.
So confirmed but it has improved a lot already.
next parent reply other threads:[~2012-02-02 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45364-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 17:36 ` pinskia at gcc dot gnu.org [this message]
2014-01-28 9:03 ` rguenth at gcc dot gnu.org
2014-01-28 13:14 ` rguenth at gcc dot gnu.org
2010-08-21 1:00 [Bug middle-end/45364] New: Apparent infinite loop while compiling wine's directx.c with -O1 -g bero at arklinux dot org
2010-08-21 1:10 ` [Bug middle-end/45364] Compiling wine's directx.c with -O1 -g takes a very long time bero at arklinux dot org
2010-08-21 5:13 ` hjl dot tools at gmail dot com
2010-08-21 14:36 ` mikpe at it dot uu dot se
2010-08-21 15:45 ` mikpe at it dot uu dot se
2010-08-21 15:57 ` jakub 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=bug-45364-4-XlacBISnOM@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).