From: Jeff Law <jeffreyalaw@gmail.com>
To: Xi Ruoyao <xry111@mengyan1223.wang>,
gcc-patches@gcc.gnu.org, marxin@gcc.gnu.org,
Matthew Fortune <mfortune@gmail.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
richard.sandiford@arm.com
Subject: Re: PING^5: [PATCH] mips: add MSA vec_cmp and vec_cmpu expand pattern [PR101132]
Date: Fri, 30 Jul 2021 09:57:17 -0600 [thread overview]
Message-ID: <f5d7e016-dc49-9a6d-73a2-1fd39963d050@gmail.com> (raw)
In-Reply-To: <mptczr0i5w7.fsf@arm.com>
On 7/30/2021 2:04 AM, Richard Sandiford via Gcc-patches 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 :-)
Yup.
>
> 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.
Right, I'm largely in the same boat as well. I've been given a degree
of freedom, but I'm very cognizant of not raising conflict of interest
concerns with my employer. Some trivial patch review for a port is OK,
but the more substantial it is, the closer it is to the line that I
don't want to cross.
Jeff
prev parent reply other threads:[~2021-07-30 15:57 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 ` committed: " Xi Ruoyao
2021-07-30 8:30 ` PING^5: " Richard Biener
2021-07-30 12:13 ` Maciej W. Rozycki
2021-07-30 15:57 ` Jeff Law [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=f5d7e016-dc49-9a6d-73a2-1fd39963d050@gmail.com \
--to=jeffreyalaw@gmail.com \
--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 \
--cc=xry111@mengyan1223.wang \
/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).