Re: [4.0 Patch] Backport testsuite "target fpic" support

["Kaveh R. Ghazi" <ghazi at caipclassic dot rutgers dot edu>]

 > > (In fact I think we should backport all changes to the
 > > testsuite/lib/ directory and other *.exp files, but that's more than
 > > I'd like to do right now.)
 > 
 > What other changes would you like to see backported?  I can probably
 > schedule time to do that, if it's acceptable to Mark to backport big
 > things that have been in mainline for a significant length of time.

Since you asked...  ideally as a goal, I'd like to be able to diff the
4.0/testsuite and mainline/testsuite and get no diffs, only added or
removed files.  Exceptions would include tests for diagnostic messages
that change between releases.  Then we should look at backporting
testcases that simply don't exist on the branch.

Backporting candidates would include stuff in the testsuite/lib
directory and the testcases themselves.  Most of the testcase changes
are to the dg- commands for finer control, better cleanup, etc.

There's a lot of changes in the testsuite/lib/ dir, some of it
functional additions and a lot of cruft as well.  The distracting
cruft is non-functional things like e.g. FSF address changes,
semicolon removal from tcl code and various comment tweeking.  That
makes it hard to see the important differences.

Anyway, it's a big job.  I'd like to at least agree that it shouldn't
further diverge.  So testsuite patches to mainline/4.1 should be
applied to 4.0 as well.  And if you want to tackle backporting lots of
old stuff, I'll help out just let me know how you want to divide the
job.

		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu