public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pletzer at txcorp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39860]  New: extremely long compile time
Date: Thu, 23 Apr 2009 04:23:00 -0000	[thread overview]
Message-ID: <bug-39860-15934@http.gcc.gnu.org/bugzilla/> (raw)

The attached code takes 20 mins to compile on a Linux/Fedora 9 box when using
-O optimization, but only 21 seconds when using -O0

[pletzer@quartic cxxps]$ time g++ -O -ftime-report -fmem-report -c cxxps.cpp >&
stat.txt

real    21m41.494s
user    16m24.774s
sys     0m19.713s

[pletzer@quartic cxxps]$ time g++ -O0 -ftime-report -fmem-report -c cxxps.cpp
>& stat.txt

real    0m21.391s
user    0m17.666s
sys     0m2.453s


-- 
           Summary: extremely long compile time
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pletzer at txcorp dot com
 GCC build triplet: Configured with: ../configure --prefix=/usr --
                    mandir=/usr/share/
  GCC host triplet: Linux quartic.txcorp.com 2.6.25.14-108.fc9.x86_64 #1 SMP
                    Mon Aug
GCC target triplet: x86_64-redhat-linux


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


             reply	other threads:[~2009-04-23  4:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  4:23 pletzer at txcorp dot com [this message]
2009-04-23  4:38 ` [Bug c++/39860] " pletzer at txcorp dot com
2009-04-23  9:35 ` rguenth 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-39860-15934@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).