public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dank@kegel.com
To: gcc@gcc.gnu.org
Cc: dank@kegel.com
Subject: re: c++ performance regressions in gcc > 2.95.3
Date: Sat, 06 Aug 2005 23:46:00 -0000	[thread overview]
Message-ID: <1781.24.126.76.52.1123371986.squirrel@webmail3.pair.com> (raw)

Anthony wrote:
> We observed that certain large C++ applications perform worse
> in gcc-3.x and gcc-4.x than they did in gcc-2.95.3.
> On the theory that at least some of the cause
> would show up in microbenchmarks, we tried running
> bench++ with both old and new toolchains.
> ...
> http://www.cis.udel.edu/~danalis/OSS/bench_plus_plus/ ...

The biggest unreported regression in in the S000005 tests:

(times are ns per iteration)
==== Fill a buffer using different levels of abstraction
           g++295   g++401   g++410_0723
S000005a 3870.00 20840.00* 21240.00*
S000005b 3878.00 21120.00* 21140.00*
S000005c 3782.00  3894.00* 21320.00*
S000005d 3862.00 21360.00* 21220.00*
S000005e 3916.00  3834.00  19780.00*
S000005f 3818.00  3936.00* 21160.00*
S000005g 3940.00 20280.00* 20640.00*
S000005h 3868.00 21040.00* 21540.00*
S000005i 3928.00 20060.00* 21480.00*
S000005j 3844.00 21840.00* 21140.00*
S000005k 3912.00  3750.00  3964.00*
S000005l 3946.00 21360.00* 3912.00
S000005m 4746.00  3958.00  3904.00

Most of these are slow in both gcc-4.0.1 and gcc-4.1.
S000005e was fine in gcc-4.0.1,
but is suddenly slower in gcc-4.1.

Anthony, can you try submitting a reduced test case for
S000005e?

Thanks,
Dan

             reply	other threads:[~2005-08-06 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06 23:46 dank [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-06  0:57 Anthony Danalis

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=1781.24.126.76.52.1123371986.squirrel@webmail3.pair.com \
    --to=dank@kegel.com \
    --cc=gcc@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).