From: HAO CHEN GUI <guihaoc@linux.ibm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Bill Schmidt <wschmidt@linux.ibm.com>
Subject: Ping [PATCH, rs6000] fix failure test cases caused by disabling mode promotion for pseudos [PR100952]
Date: Mon, 19 Jul 2021 10:41:50 +0800 [thread overview]
Message-ID: <aceadbab-b0b4-32b2-7318-ea0740f2c3b9@linux.ibm.com> (raw)
In-Reply-To: <3544e148-761a-1691-0b49-7d131739dd76@linux.ibm.com>
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/574503.html
Thanks.
On 6/7/2021 上午 11:11, HAO CHEN GUI wrote:
>
> Hi
>
> The patch changed matching conditions in pr81384.c and pr56605.c.
> The original conditions failed to match due to mode promotion disabled.
>
> The attachments are the patch diff and change log file.
>
> Bootstrapped and tested on powerpc64le-linux with no regressions.
> Is this okay for trunk? Any recommendations? Thanks a lot.
>
next prev parent reply other threads:[~2021-07-19 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 3:11 HAO CHEN GUI
2021-07-19 2:41 ` HAO CHEN GUI [this message]
2021-07-21 22:51 ` Segher Boessenkool
2021-07-23 0:46 ` HAO CHEN GUI
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=aceadbab-b0b4-32b2-7318-ea0740f2c3b9@linux.ibm.com \
--to=guihaoc@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.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).