This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [RFC] testsuite/performance
- From: Phil Edwards <phil at jaj dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Sun, 18 May 2003 00:00:46 -0400
- Subject: Re: [RFC] testsuite/performance
- References: <20030516124137.5ada7875.bkoz@redhat.com>
On Fri, May 16, 2003 at 12:41:37PM -0500, Benjamin Kosnik wrote:
> There's long been talk of storing performance-related tests in the
> testsuite itself. Here's a first crack at actually doing this. In
> preparing this patch, I did a lot of CVS/web/mailing list excavation
> (including the finding of Loren's post to switch back to the pool
> allocator on 2001-05-03, which it seems is the basis for the subsequent
> allocator tests). It was pretty interesting, but perhaps I forgot
> somethings. If so, let me know.
I just started adapting Stefan Olsson's tests, posted with his mt_alloc
patch on 4 March. Then my machine crashed. Should have access to my source
code again within a week or so.
> 2) Some of these tests produce large output files (75MB) (which are
> removed with make clean, of course.) Some require large input files.
> Should they be run by default?
I'm with Jerry on this: none of them should be run by default since
baseline times won't be available anyhow.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams