public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/28871]  New: massive C++ compile time slowdown
Date: Mon, 28 Aug 2006 12:42:00 -0000	[thread overview]
Message-ID: <bug-28871-365@http.gcc.gnu.org/bugzilla/> (raw)

Sometime between Aug 1, 2006 and Aug 22, 2006 the time needed to run the g++
and libstdc++ testsuite ballooned. 

See this message and followups:
http://gcc.gnu.org/ml/gcc/2006-08/msg00398.html

Here are the specifics that I have:

20060724, make check-target-libstdc++
1145.687u 137.804s 23:13.98 92.0%       0+0k 0+0io 23pf+0w

20060822, make check-target-libstdc++
2624.876u 247.539s 55:42.82 85.9%       0+0k 0+0io 45pf+0w

Ouch. In that time, there have been some additions in the libstdc++ testsuite,
however it did not double in size. I've been trying to compile mainline
libstdc++ with 4.1.1 g++ to see if I can pin down the issue to a particular
component but there are a lot of incompatible changes, so comparing directly is
difficult to impossible.


-- 
           Summary: massive C++ compile time slowdown
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bkoz at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2006-08-28 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 12:42 bkoz at gcc dot gnu dot org [this message]
2006-08-28 13:24 ` [Bug c++/28871] " pinskia at gcc dot gnu dot org
2006-08-29 10:36 ` bkoz at gcc dot gnu dot org
2006-08-29 10:44 ` bkoz at gcc dot gnu dot org
2006-09-04 15:25 ` bkoz at gcc dot gnu dot org
2006-09-04 15:26 ` bkoz at gcc dot gnu dot org
2006-09-04 15:41 ` bkoz 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-28871-365@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).