This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [GCC 3.x] Performance testing for QA
- From: dewar at gnat dot com (Robert Dewar)
- To: dewar at gnat dot com, kevina at gnu dot org
- Cc: Peter dot Sasi at t-systems dot co dot hu, aj at suse dot de, gcc at gcc dot gnu dot org,tjw at omnigroup dot com
- Date: Tue, 3 Sep 2002 17:25:45 -0400 (EDT)
- Subject: Re: [GCC 3.x] Performance testing for QA
<<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 :-)