From: liu & zhensong <liuzhensong@sourceware.org>
To: binutils-cvs@sourceware.org
Subject: [binutils-gdb] LoongArch: Remove unused code in ld test suite
Date: Mon, 1 Jul 2024 02:13:13 +0000 (GMT) [thread overview]
Message-ID: <20240701021313.4B57E3858C39@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d8eca1671571ce6adf5dbcad649dbdfa56a07614
commit d8eca1671571ce6adf5dbcad649dbdfa56a07614
Author: Xi Ruoyao <xry111@xry111.site>
Date: Sat Jun 22 18:06:47 2024 +0800
LoongArch: Remove unused code in ld test suite
These seems some left over from MIPS code and they do not make any
sense for LoongArch.
Signed-off-by: Xi Ruoyao <xry111@xry111.site>
Diff:
---
ld/testsuite/ld-loongarch-elf/anno-sym.d | 2 --
ld/testsuite/ld-loongarch-elf/ld-loongarch-elf.exp | 7 -------
2 files changed, 9 deletions(-)
diff --git a/ld/testsuite/ld-loongarch-elf/anno-sym.d b/ld/testsuite/ld-loongarch-elf/anno-sym.d
index a58f4a6c25a..6d2149f0766 100644
--- a/ld/testsuite/ld-loongarch-elf/anno-sym.d
+++ b/ld/testsuite/ld-loongarch-elf/anno-sym.d
@@ -3,5 +3,3 @@
#as: -mno-relax
#ld: -e _start
#error_output: anno-sym.l
-# The mips-irix6 target fails this test because it does not find any function symbols. Not sure why.
-#skip: *-*-irix*
diff --git a/ld/testsuite/ld-loongarch-elf/ld-loongarch-elf.exp b/ld/testsuite/ld-loongarch-elf/ld-loongarch-elf.exp
index d833a89246e..2d67c4f2668 100644
--- a/ld/testsuite/ld-loongarch-elf/ld-loongarch-elf.exp
+++ b/ld/testsuite/ld-loongarch-elf/ld-loongarch-elf.exp
@@ -19,13 +19,6 @@
# MA 02110-1301, USA.
#
-proc loongarch_choose_lp64_emul {} {
- if { [istarget "loongarch64be-*"] } {
- return "elf64bloongarch"
- }
- return "elf64lloongarch"
-}
-
if [istarget "loongarch64-*-*"] {
run_dump_test "jmp_op"
run_dump_test "macro_op"
reply other threads:[~2024-07-01 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240701021313.4B57E3858C39@sourceware.org \
--to=liuzhensong@sourceware.org \
--cc=binutils-cvs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).