public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gisli@adams.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/2183: gcc-3_0-branch compiles 2x slower than 2.95
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <20010305180445.19549.qmail@sourceware.cygnus.com> (raw)

>Number:         2183
>Category:       c++
>Synopsis:       gcc-3_0-branch compiles 2x slower than 2.95
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 05 10:06:02 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     gisli@adams.com
>Release:        CVS gcc-3_0-branch on March 3rd
>Organization:
>Environment:
System: Linux 2.2.16-22smp
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: configure --prefix=/opt/gcc3.0 --enable-shared

>Description:
This is my first experience with GCC 3.0.  I am compiling
a ca. 100,000 line C++ program which takes modest advantage
of templates (STL mostly) and exceptions.  By virtue of
being ported to a variety of platforms, the code compiled
with 3.0 pretty much out of the box.

However, compile time is noticably higher, going from 
exactly 15 minutes with 2.95 to exactly 30 minutes with 3.0.

Pertinent compile flags are:  -ggdb -ansi -pedantic -W

I have not compared the compile time for optimization,
because this does not affect my daily work.

I am available to do any kind of testing/experiments that
you would like me to.  If you are interested, I should be
able to provide pre-processed source, e.g. for the following
file:

AsExpression.o

2.95, -ggdb -ansi -pedantic -W              25.02s
3.0-branch, -ggdb -ansi -pedantic -W        44.24s

2.95, -O2                                  207.28s 
3.0-branch, -O2                            392.45s

Unfortunately, due to a lack of a binary compatible 
support library, I have not yet been able to test the
performance of the resulting executable.

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  0:00 gisli [this message]
2002-11-01 17:40 bangerth

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=20010305180445.19549.qmail@sourceware.cygnus.com \
    --to=gisli@adams.com \
    --cc=gcc-gnats@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).