From: Marc Lehmann <pcg@goof.com>
To: egcs@cygnus.com
Subject: announce: egcs benchmark suite, alpha release
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <19990116065208.A17513@cerebro.laendle> (raw)
I'm pleased to announce the first public release of the egcs benchmark suite.
WHAT IS IT?
The egcs benchmark suite is a collection of individual tests used to
determine relative performance changes of specific optimizations. There are
tests that check performance of different datatypes on the same problem,
tests that measure the C++ abstraction penalty, tests measuring function
inlining/call overhead and more...
Regular benchmarking will also allow to detect optimization problems.
WHAT IS IT _NOT_?
It's not a general purpose benchmark library. It's unsuitable for comparing
performance of one machine/os to another, and it's also unsuitable to compare
performance between different compilers. Its sole purpose is to measure speed
enhancements (or deficiencies) between egcs compiler revisions.
In short, what the testsuite is for compiler correctness, is the benchmark
suite for optimizer quality.
WHAT WE NEED
at the moment are people that alpha test the release, give compatibility
hints, detect problems with the setup.
if the suite turns out to be useful, we need regular testers so we can fill
the benchmark database and write cute perl programs that draw even cuter
graphs ;)
Also we need input on how to handle compiler switches, i.e. should
we run a single test with -O2, or multiple tests with -O2, -O3, -O3
-funroll-loops etc. (and how do we keep the results comparable in the
latter case)
WHERE TO GET IT?
At the moment its "only" available via cvs. Instead of checking out the
"egcs" directory you can check out the "benchmarks" directory. (Just follow
the instructions for checking out "egcs" but replace it by "benchmarks")
HOW TO USE IT?
Yes, the README is not quite up-to-date, but everything you should have to do is to type:
make
which will compile & run all benchmarks and automatically mail me the
results, testing everything in the package.
THANKS
OH YES, thanks a lot to Jan Hubicka, who not only had the original idea to
create the benchmark suite, but also delivered all the initial tests and
programmed the initial testing framework.
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 Marc Lehmann [this message]
1999-01-20 18:54 ` Arvind Sankar
1999-01-20 19:12 ` Arvind Sankar
1999-01-31 23:58 ` Arvind Sankar
1999-01-31 23:58 ` Arvind Sankar
1999-01-28 5:53 ` egcs benchmark suite, nits Marc Espie
1999-01-31 23:58 ` Marc Espie
1999-01-31 23:58 ` announce: egcs benchmark suite, alpha release Dave Love
1999-01-31 23:58 ` Jeffrey A Law
1999-01-22 12:25 ` Marc Lehmann
1999-01-24 8:28 ` Dave Love
1999-01-24 14:52 ` Marc Lehmann
1999-01-31 23:58 ` Marc Lehmann
1999-01-31 23:58 ` Dave Love
1999-01-31 23:58 ` Marc Lehmann
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=19990116065208.A17513@cerebro.laendle \
--to=pcg@goof.com \
--cc=egcs@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).