[LLVMdev] [RFC] Benchmarking subset of the test suite

Reid Kleckner rnk at google.com
Mon May 5 12:44:05 PDT 2014


On Sun, May 4, 2014 at 1:33 PM, Hal Finkel <hfinkel at anl.gov> wrote:

> ----- Original Message -----
> > From: "Chris Lattner" <clattner at apple.com>
> > To: "Hal Finkel" <hfinkel at anl.gov>
> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
> > Sent: Sunday, May 4, 2014 1:37:42 PM
> > Subject: Re: [LLVMdev] [RFC] Benchmarking subset of the test suite
> >
> > On May 4, 2014, at 5:39 AM, Hal Finkel <hfinkel at anl.gov> wrote:
> > > Without further ado, I propose that a test-suite configuration
> > > designed for benchmarking exclude the following:
> >
> > Unrelatedly to your point, I think we should just outright remove the
> > bulk of the SingleSource/Regression / SingleSource/UnitTests tests.
> >  They largely date back to before Clang existed and aren’t serving
> > much useful value anymore.
> >
> > Any of them that are useful (e.g. the EH tests?) could be saved or
> > moved somewhere else.
>
> I have mixed feelings about this. On the one hand, the regression and unit
> tests don't belong with the others, and if we start running applications
> multiple times for benchmarking, we'd likely want to exclude these
> correctness-only tests. On the other hand, I've found some of these tests
> quite useful in catching miscompiles (the EH tests, the bitfield tests,
> vector intrinsics tests and the va_args tests specifically come to mind).
> It might be useful to separate out some set of 'ABI' tests, even if we
> remove the others.
>

+1 for small, single-source ABI execution tests.  There's definitely a
place for them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140505/8b939d84/attachment.html>


More information about the llvm-dev mailing list