From: YunQiang Su <syq@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] MIPS: fix loongson3 llsc workaround
Date: Sun, 23 Apr 2023 06:53:22 +0000 (GMT) [thread overview]
Message-ID: <20230423065322.5F9023858C50@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=af989297316ec7628f1ddffc621932805a464b1d
commit af989297316ec7628f1ddffc621932805a464b1d
Author: YunQiang Su <yunqiang.su@cipunited.com>
Date: Thu Mar 23 18:49:23 2023 +0800
MIPS: fix loongson3 llsc workaround
-mfix-looongson3-llsc may add sync instructions not needed on some
asm code with lots of debug info.
PR: 30153
* gas/config/tc-mips.c(fix_loongson3_llsc): clear logistic.
Diff:
---
gas/config/tc-mips.c | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
diff --git a/gas/config/tc-mips.c b/gas/config/tc-mips.c
index e911aaa904a..8a970ceada2 100644
--- a/gas/config/tc-mips.c
+++ b/gas/config/tc-mips.c
@@ -6942,10 +6942,6 @@ fix_loongson3_llsc (struct mips_cl_insn * ip)
unsigned long lookback = ARRAY_SIZE (history);
for (i = 0; i < lookback; i++)
{
- if (streq (history[i].insn_mo->name, "ll")
- || streq (history[i].insn_mo->name, "lld"))
- break;
-
if (streq (history[i].insn_mo->name, "sc")
|| streq (history[i].insn_mo->name, "scd"))
{
@@ -6953,8 +6949,8 @@ fix_loongson3_llsc (struct mips_cl_insn * ip)
for (j = i + 1; j < lookback; j++)
{
- if (streq (history[i].insn_mo->name, "ll")
- || streq (history[i].insn_mo->name, "lld"))
+ if (streq (history[j].insn_mo->name, "ll")
+ || streq (history[j].insn_mo->name, "lld"))
break;
if (delayed_branch_p (&history[j]))
@@ -6993,7 +6989,7 @@ fix_loongson3_llsc (struct mips_cl_insn * ip)
for (j = i + 1; j < lookback; j++)
{
if (streq (history[j].insn_mo->name, "ll")
- || streq (history[i].insn_mo->name, "lld"))
+ || streq (history[j].insn_mo->name, "lld"))
break;
}
reply other threads:[~2023-04-23 6:53 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=20230423065322.5F9023858C50@sourceware.org \
--to=syq@sourceware.org \
--cc=bfd-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).