PATCH: Run V3 tests on installed compiler

Mark Mitchell mark@codesourcery.com
Wed Mar 23 20:29:00 GMT 2005


Phil Edwards wrote:
> On Wed, Mar 23, 2005 at 08:50:14AM -0800, Mark Mitchell wrote:
> 
>>Any objections?
> 
> 
> Benjamin has already raised the workflow concerns, which I second.
> Making changes to this set of files and then rerunning the testsuite on
> the reduced set of tests is SOP for maintainers.  If it's still available,
> that would be highly desirable.

See follow-up comments; does the:

   normal.exp="`cat testsuite_files`"

thing meet your needs?

(This is, of course, not a V3-specific problem; compiler people like to 
run just tests in particular categories too.)

>>(Minor note: libstdc++.exp uses "v3-" as a prefix for some functions;
>>it should really be using "libstdc++_" as that is the convention for
>>tool configuration files.)

> This convention is documented in lib/libstdc++.exp:
> 
> # The naming rule is that dg.exp looks for "tool-" and runtest.exp looks
> # for "tool_" when finding callbacks.  Utility routines we define for
> # our callbacks begin with "v3-".
> 
> (And that third line should have "the use of" prepended, really.)  We wanted
> a consistent naming scheme which would be guaranteed to never be found
> by DejaGNU.

I'm increasing my dosage of humility pills.

Is this patch OK, assuming testing succeeds?

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: v3.patch
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050323/65d1cf2c/attachment.ksh>


More information about the Libstdc++ mailing list