Mark the linker's extract symbols test as an expected failure for MIPS targets.

	* testsuite/ld-scripts/script.exp (extract_symbol_test): Expect to
	fail for MIPS targets.

diff --git a/ld/ChangeLog b/ld/ChangeLog
index 86426ffde230dbdd132770b44b5fc4ad1c4d53e2..a0222a15bba8dbddd7f3c4878a442d704996b1ca 100644 (file)
--- a/ld/ChangeLog
+++ b/ld/ChangeLog
@@ -1,5 +1,8 @@
 2016-01-13  Nick Clifton  <nickc@redhat.com>
 
+       * testsuite/ld-scripts/script.exp (extract_symbol_test): Expect to
+       fail for MIPS targets.
+
        * testsuite/ld-scripts/rgn-at11.d: Expect this test to fail for
        MIPS targets.
 

diff --git a/ld/testsuite/ld-scripts/script.exp b/ld/testsuite/ld-scripts/script.exp
index 03d5d4e0a64ba4a66f58ac43d4b6415126f01af0..fc95658774cb96d027fba24f7a6d789d048a8170 100644 (file)
--- a/ld/testsuite/ld-scripts/script.exp
+++ b/ld/testsuite/ld-scripts/script.exp
@@ -134,6 +134,17 @@ proc extract_symbol_test { testfile testname } {
            # but absolute symbol types are expected.
            regsub -all " \[TD\] " $syms_massaged " A " syms_massaged
        }
+       ^mips-*-* {
+           # This test cannot proceed any further for MIPS targets.
+           # The extract_syms operation produces a binary with a zero
+           # length .reginfo section, which is illegal under the MIPS
+           # ABI.  Since producing such sections is part of the expected
+           # behaviour of --extract-symbols, no further testing can be
+           # performed.  Fortunately this should not matter as extracting
+           # symbols is only needed for VxWorks support.
+           pass $testname
+           return
+       }
     }
 
     set extract_syms [run_host_cmd $nm $copyfile]
@@ -142,6 +153,7 @@ proc extract_symbol_test { testfile testname } {
        return
     }
 
+    # Check that the stripped section contains no code or data.
     set exec_output [run_host_cmd $size $copyfile]
     if ![regexp ".* 0\[         \]+0\[  \]+0\[  \]+0\[  \]+0\[  \]+.*" $exec_output] {
        fail $testname