This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] MIPS: MIPS32r2 FP MADD instruction set support
- From: Mike Stump <mikestump at comcast dot net>
- To: Maciej W. Rozycki <macro at codesourcery dot com>
- Cc: Richard Sandiford <rdsandiford at googlemail dot com>, Steve Ellcey <Steve dot Ellcey at imgtec dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 21 Feb 2013 13:47:09 -0800
- Subject: Re: [PATCH] MIPS: MIPS32r2 FP MADD instruction set support
- References: <alpine.DEB.email@example.com>
On Feb 20, 2013, at 3:50 PM, Maciej W. Rozycki <firstname.lastname@example.org> wrote:
> BTW, do you happen to know a way to reliable force all our testsuites NOT
> to delete executables after run? Personally I think it's missing the
> point to have them deleted -- how can one debug any regressions then?
So, I go into the source and comment out the cleanup lines… Would be nice to have them conditional on a variable so that one can set that variable in their .dejagnurc file.
The limitations of this are, multiple test cases can use the same intermediate files and they would not give you a nice 1 to 1 mapping back. However, this I usually side step by only running a subset of the test suite that contains the part I'm interested in.
> What do other people do?
We usually can cut and paste the one line and run the one case by hand. Test cases that don't fall into this category, well, suck, I mean, are more annoying.