[Bug gas/22304] New: XPASS tests in gas and unknown successes in ld

[hjl.tools at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=22304

            Bug ID: 22304
           Summary: XPASS tests in gas and unknown successes in ld
           Product: binutils
           Version: 2.30 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gas
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---
            Target: cris

On x86-64, cross binutils to cris-linux gave

XPASS: gas/cris/shexpr-1
XPASS: gas/cris/range-err-1.s  (test for errors, line 29)
XPASS: gas/cris/range-err-1.s  (test for errors, line 38)
XPASS: gas/cris/range-err-1.s  (test for errors, line 50)

These should be removed.  Similar check can be used to detect 64-bit AS:

commit 7ed1dab994fa1c0cf49d10608b8e77271c9804b4
Author: H.J. Lu <address@hidden>
Date:   Wed Aug 9 16:32:30 2017 -0700

    LD_CLASS: Check .libs/ld-new for linker first

    When --enable-shared is used, ./ld-new may be a shell script and the
    real linker is .libs/ld-new.  We should check .libs/ld-new first.

            * testsuite/config/default.exp (LD_CLASS): Check .libs/ld-new
            for linker first.

commit 978c05401b0f0ac7a94cca7db19b1dec0c5bd698
Author: H.J. Lu <address@hidden>
Date:   Wed Aug 9 15:04:05 2017 -0700

    Run PR ld/17618 test only with 64-bit ELF linker

    PR ld/17618 test requires 64-bit linker to run.  Set LD_CLASS to "64bit"
    for 64-bit ELF linker and run PR ld/17618 test only if $LD_CLASS is
    "64bit".  More checks can be added to support 64-bit linkers in non-ELF
    format.

On both i686 and x86-64, there are

                === ld Summary ===

# of expected passes            644
# of expected failures          3
# of unknown successes          3
# of untested testcases         26
# of unsupported tests          42

These unknown successes should be removed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.