From: dewar@gnat.com (Robert Dewar)
To: dewar@gnat.com, kevina@gnu.org
Cc: Peter.Sasi@t-systems.co.hu, aj@suse.de, gcc@gcc.gnu.org,
tjw@omnigroup.com
Subject: Re: [GCC 3.x] Performance testing for QA
Date: Tue, 03 Sep 2002 14:25:00 -0000 [thread overview]
Message-ID: <20020903212545.6E76BF2DA6@nile.gnat.com> (raw)
<<Than you need to use a wide variety of encoders to avoid this problem.
Also since the source code for gcc is freely available such a thing will
not go unnoticed for long. I seams that you are trying to say that making
tight loops run fast is a pointless exercise by the compiler. If a large
number of programs tend to use a particular type of loop than optimizing
for those loops would be a huge win in terms of performance.
>>
There are plenty of benchmarks in SPEC and in other standard suites that
have tight loops. So you are misinterpreting my remarks entirely.
The point is that benchmarks are designed to be good as benchmarks, the issue
of whether they perform a useful calculation that lots of people run a lot of
the time is quite besides the point. I would guess that you have not even
studied the SPEC suite closely before you made remarks about it :-)
next reply other threads:[~2002-09-03 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 14:25 Robert Dewar [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 14:15 Robert Dewar
2002-09-03 13:56 Robert Dewar
2002-09-03 13:55 Robert Dewar
2002-09-03 14:05 ` Kevin Atkinson
2002-09-03 14:12 ` Dale Johannesen
2002-09-03 13:36 Robert Dewar
2002-09-03 13:41 ` Kevin Atkinson
2002-09-03 13:25 Robert Dewar
2002-09-03 13:31 ` Daniel Jacobowitz
2002-09-03 14:28 ` Jan Hubicka
2002-09-02 15:50 Robert Dewar
2002-09-02 15:49 Robert Dewar
2002-09-03 10:32 ` Dale Johannesen
2002-09-03 11:17 ` Kevin Atkinson
2002-09-02 14:47 Robert Dewar
2002-09-02 15:42 ` Timothy J. Wood
2002-09-02 6:12 Sasi Péter
2002-09-02 14:08 ` Andreas Jaeger
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=20020903212545.6E76BF2DA6@nile.gnat.com \
--to=dewar@gnat.com \
--cc=Peter.Sasi@t-systems.co.hu \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=kevina@gnu.org \
--cc=tjw@omnigroup.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).