gcc/libgo/testsuite
Ian Lance Taylor d694576e17 gotest: force test package to be imported first
When compiling the x_test package, force the test package to be
    imported first.  That ensures that we will see the types defined in
    the test package before the types defined in the non-test version of
    the package.  This matters if the types differ in some way, such as by
    adding a new method.
    
    This avoids a failure in internal/poll on Solaris, in which the test
    package adds a method to a type (FD.EOFError).  I think it was Solaris-
    specific because files are sorted in a different order by default.
    
    The go tool handles this kind of thing correctly, by rebuilding
    dependent packages.  This is just a hack sufficient to run the libgo
    testsuite without using the go tool.
    
    Fixes https://gcc.gnu.org/PR91712
    
    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/194637

From-SVN: r275648
2019-09-11 12:44:12 +00:00
..
config
lib Testsuite: add dg-{begin|end}-multiline-output commands 2015-10-09 13:55:23 +00:00
libgo.testmain libgo: Set name of test when using DejaGNU tests. 2011-03-31 23:03:20 +00:00
gotest gotest: force test package to be imported first 2019-09-11 12:44:12 +00:00
Makefile.am
Makefile.in runtime: drop unused C type reflection code 2019-05-31 21:32:47 +00:00