From: Xi Ruoyao <xry111@xry111.site>
To: YunQiang Su <syq@debian.org>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
Cc: YunQiang Su <yunqiang.su@cipunited.com>,
gcc-patches@gcc.gnu.org, macro@orcam.me.uk,
jiaxun.yang@flygoat.com, richard.sandiford@arm.com,
jeffreyalaw@gmail.com
Subject: Re: [PATCH v5] MIPS: Add speculation_barrier support
Date: Fri, 16 Jun 2023 16:38:30 +0800 [thread overview]
Message-ID: <ac6ec5a7fdfd1e532b882b8184a1fa356656caee.camel@xry111.site> (raw)
In-Reply-To: <CAKcpw6Wt0BOV=tW2PTqC9RbZNkcYsRQT1GBsABfBuj6OdQ+_cg@mail.gmail.com>
On Fri, 2023-06-16 at 15:53 +0800, YunQiang Su wrote:
> Ohh, sorry. I forget it. I commented there.
> I have no permission to close this bug report. Can you help to close
> it?
Modify the email address of your Bugzilla account to your @gcc.gnu.org
address, then you should be able to close it.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-06-16 8:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 12:33 [PATCH] MIPS: add " YunQiang Su
2023-04-28 12:36 ` Jiaxun Yang
2023-04-28 13:07 ` YunQiang Su
2023-04-28 13:12 ` [PATCH v2] " YunQiang Su
2023-05-03 18:29 ` Richard Sandiford
2023-05-03 21:04 ` Maciej W. Rozycki
2023-05-03 22:12 ` Jiaxun Yang
2023-05-07 17:34 ` Maciej W. Rozycki
2023-05-07 18:47 ` Jiaxun Yang
2023-05-07 19:16 ` Maciej W. Rozycki
2023-05-12 10:03 ` [PATCH v3] " YunQiang Su
2023-05-12 10:30 ` [PATCH v4] " YunQiang Su
2023-05-31 9:43 ` YunQiang Su
2023-05-31 10:35 ` Maciej W. Rozycki
2023-06-01 4:26 ` [PATCH v5] MIPS: Add " YunQiang Su
2023-06-08 12:35 ` Richard Earnshaw (lists)
2023-06-16 7:53 ` YunQiang Su
2023-06-16 8:38 ` Xi Ruoyao [this message]
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=ac6ec5a7fdfd1e532b882b8184a1fa356656caee.camel@xry111.site \
--to=xry111@xry111.site \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=macro@orcam.me.uk \
--cc=richard.sandiford@arm.com \
--cc=syq@debian.org \
--cc=yunqiang.su@cipunited.com \
/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).