From: Dan Kegel <dank@kegel.com>
To: mfletcher@serck-controls.co.uk
Cc: gdb@sources.redhat.com, "Stewart, Richard" <rstewart@mc.com>
Subject: Re: GDB 4.18 with GCC 3.3.6
Date: Fri, 08 Jul 2005 14:50:00 -0000 [thread overview]
Message-ID: <42CE90AF.6040909@kegel.com> (raw)
In-Reply-To: <200507081536.52039.mfletcher@serck-controls.co.uk>
Matthew J Fletcher wrote:
>>I'm putting together a performance regression benchmark
>>suite right now by pulling together all the known microbenchmarks
>>that run slower on newer versions of gcc, in hopes
>>of helping make sure that gcc-4.1 resolves most of them.
>
> i would be very interested in your preliminary results if you have any.
>
> maybe your going to test 2.95.3 / 3.3.6 / 3.4.4 / 4.0.1 / 4.1.x with C based
> benchmarks, but i would be also very intrested in complex C++ (using stl
> features) for the same set of compilers, as my 'embedded' application is
> written in complex c++.
Some of our tests come from bug reports in gcc bugzilla,
but most so far come from bench++. At least a couple
involve c++. You can see those by running bench++ yourself,
it's pretty good once you get past the setup hurdles
(like, it wants you to install ksh!). It's at
http://www.research.att.com/~orost/bench_plus_plus.html
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
next prev parent reply other threads:[~2005-07-08 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 12:08 Stewart, Richard
2005-07-08 13:42 ` Dan Kegel
2005-07-08 14:33 ` Matthew J Fletcher
2005-07-08 14:50 ` Dan Kegel [this message]
2005-07-08 13:56 ` Daniel Jacobowitz
2005-07-08 19:02 ` Jason Molenda
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=42CE90AF.6040909@kegel.com \
--to=dank@kegel.com \
--cc=gdb@sources.redhat.com \
--cc=mfletcher@serck-controls.co.uk \
--cc=rstewart@mc.com \
/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