[PATCH] Fix riscv binutils xfail for debug_ranges test.

[Jim Wilson]

The debug_ranges test is marked as an expected fail, but it now passing.
The original problem was fixed by this patch

commit 575934368531e7592a7576a39a4320d88007ce88
Author: Kuan-Lin Chen <rufus@andestech.com>
Date:   Mon Jul 31 15:33:48 2017 +0100

    Improve handling of ADD and SUB relocations on the RISCV target.

so we no longer need to mark this as expected fail.  Tested on riscv32-elf,
riscv64-elf, and x86_64-linux.  Applied.

	binutils/
	* testsuite/binutils-all/objdump.exp: Expect the debug_ranges test to
	pass.
---
 binutils/testsuite/binutils-all/objdump.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/binutils/testsuite/binutils-all/objdump.exp b/binutils/testsuite/binutils-all/objdump.exp
index 83b9af6f55..47cda4562d 100644
--- a/binutils/testsuite/binutils-all/objdump.exp
+++ b/binutils/testsuite/binutils-all/objdump.exp
@@ -335,7 +335,7 @@ if { ![is_elf_format] } then {
 	send_log "\n"
     }
 
-    setup_xfail "msp430-*-*" "nds32*-*-*" "riscv*-*-*"
+    setup_xfail "msp430-*-*" "nds32*-*-*"
     if { [regexp_diff objdump.out $srcdir/$subdir/dw2-ranges.W] } then {
 	fail "objdump -W for debug_ranges"
     } else {
-- 
2.14.1