public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <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: Sat, 21 Aug 2010 14:36:00 -0000	[thread overview]
Message-ID: <20100821143614.27396.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45364-5606@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from mikpe at it dot uu dot se  2010-08-21 14:36 -------
Well something in -g processing is a CPU hog.  On my Turion X2 Ultra ZM-82
laptop (2.2GHz x 2 cores) with 32-bit kernel and vanilla gcc-4.5.1
(--enable-checking=release) I get:

> time gcc -m32 -O0  -c pr45364.i
1.220u 0.120s 0:01.35 99.2%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O0 -g -c pr45364.i
1.500u 0.060s 0:01.57 99.3%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -c pr45364.i
3.100u 0.100s 0:03.21 99.6%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O1 -g -c pr45364.i
22.590u 0.190s 0:22.81 99.8%    0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -c pr45364.i
8.680u 0.210s 0:08.93 99.5%     0+0k 0+0io 0pf+0w
> time gcc -m32 -O2 -g -c pr45364.i
238.490u 0.340s 3:58.97 99.9%   0+0k 0+0io 0pf+0w

During the last -O2 -g run I ran top and cc1 only used about 200MB, so swapping
is not the problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45364


  parent reply	other threads:[~2010-08-21 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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:01 ` [Bug middle-end/45364] " 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 [this message]
2010-08-21 15:45 ` mikpe at it dot uu dot se
2010-08-21 15:57 ` jakub at gcc dot gnu dot org
     [not found] <bug-45364-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 17:36 ` pinskia at gcc dot gnu.org
2014-01-28  9:03 ` rguenth at gcc dot gnu.org
2014-01-28 13:14 ` 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=20100821143614.27396.qmail@sourceware.org \
    --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).