aboutsummaryrefslogtreecommitdiff
path: root/sim/m32c/misc.c
diff options
context:
space:
mode:
authorAlan Modra <amodra@gmail.com>2021-02-12 17:05:12 +1030
committerAlan Modra <amodra@gmail.com>2021-02-12 18:56:05 +1030
commit17e04eff810ecf1f8392a995876a98361c565ec7 (patch)
tree534b89c06a3df24e8f61d556b71156992f256b0f /sim/m32c/misc.c
parent8f054a7a5a973ffc590e90b8cec3d622a8da6c5c (diff)
downloadbinutils-17e04eff810ecf1f8392a995876a98361c565ec7.zip
binutils-17e04eff810ecf1f8392a995876a98361c565ec7.tar.gz
binutils-17e04eff810ecf1f8392a995876a98361c565ec7.tar.bz2
binutils testsuite: replace unresolved with unsupported
You'd think "unresolved" would be correct for an objcopy test when the assembler refuses to assemble one of our source files. After all, the test of objcopy hasn't been run. However, "unresolved" results in runtest returning with an error status. If instead we report "unsupported", runtest returns success. Which is a little less confusing to a user who doesn't see any errors reported unless they look in log files. * testsuite/binutils-all/objcopy.exp: Report "unsupported" when gas or ld fails to build a testcase rather than "unresolved". Report "fail" when readelf returns an error status rather than "unresolved". * testsuite/binutils-all/ar.exp: Likewise. * testsuite/binutils-all/compress.exp: Likewise. * testsuite/binutils-all/readelf.exp: Likewise.
Diffstat (limited to 'sim/m32c/misc.c')
0 files changed, 0 insertions, 0 deletions