From: Xi Ruoyao <xry111@mengyan1223.wang>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: marxin@gcc.gnu.org, Matthew Fortune <mfortune@gmail.com>,
gcc-patches@gcc.gnu.org, "Maciej W. Rozycki" <macro@orcam.me.uk>
Subject: committed: [PATCH] mips: add MSA vec_cmp and vec_cmpu expand pattern [PR101132]
Date: Sat, 31 Jul 2021 02:06:30 +0800 [thread overview]
Message-ID: <1ecb8e9ec2fcc7c27aca83f65ffa2fc0f6288754.camel@mengyan1223.wang> (raw)
In-Reply-To: <c083490ff12c7d5b819193a17c559c19a56263f2.camel@mengyan1223.wang>
On Fri, 2021-07-30 at 16:17 +0800, Xi Ruoyao via Gcc-patches wrote:
> On Fri, 2021-07-30 at 09:04 +0100, Richard Sandiford wrote:
> > Xi Ruoyao <xry111@mengyan1223.wang> writes:
> > > Ping again.
> >
> > Sorry that this has gone unreviewed for so long. I think in
> > practice
> > the MIPS port is essentially unmaintained at this point -- it would
> > be great if someone would volunteer :-)
>
> A company working on MIPS has contacted me and said one of their
> employees may contact the SC and take the role of MIPS maintainer.
> Not
> sure their progress though.
>
> > It isn't really appropriate for me to review MIPS stuff given that I
> > work
> > for a company that has a competing architecture. I think Jeff
> > expressed
> > similar concerns given his new role.
>
> > That said, the patch looks clearly correct to me, so please go ahead
> > and apply (to trunk and GCC 11). Thanks for your patience.
>
> Thanks!
>
> It has been 5 weeks so it's better to rebase and bootstrap & test it
> again. I'll commit it if there is no regression.
Committed to master at 45cb789e and releases/gcc-11 at 2a47ee78.
--
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2021-07-30 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 13:42 Xi Ruoyao
2021-07-01 8:11 ` Xi Ruoyao
2021-07-09 6:50 ` PING^2: " Xi Ruoyao
2021-07-16 5:57 ` PING^3: " Xi Ruoyao
2021-07-23 12:46 ` PING^4: " Xi Ruoyao
2021-07-30 4:56 ` PING^5: " Xi Ruoyao
2021-07-30 8:04 ` Richard Sandiford
2021-07-30 8:17 ` Xi Ruoyao
2021-07-30 18:06 ` Xi Ruoyao [this message]
2021-07-30 8:30 ` Richard Biener
2021-07-30 12:13 ` Maciej W. Rozycki
2021-07-30 15:57 ` Jeff Law
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=1ecb8e9ec2fcc7c27aca83f65ffa2fc0f6288754.camel@mengyan1223.wang \
--to=xry111@mengyan1223.wang \
--cc=gcc-patches@gcc.gnu.org \
--cc=macro@orcam.me.uk \
--cc=marxin@gcc.gnu.org \
--cc=mfortune@gmail.com \
--cc=richard.sandiford@arm.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).