From: Jim Wilson <jim.wilson@linaro.org>
To: Jiong Wang <jiong.wang@foss.arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>,
Kyrill Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: [PATCH] PR67305, tighten neon_vector_mem_operand on eliminable registers
Date: Wed, 04 Nov 2015 22:39:00 -0000 [thread overview]
Message-ID: <563A88FE.7050409@linaro.org> (raw)
In-Reply-To: <5639D3A8.5040606@foss.arm.com>
On 11/04/2015 01:45 AM, Jiong Wang wrote:
> So as Jim Wilson commented on the bugzilla, instead of "return !strict",
> we need to only do the check if strict be true, and only does rejection
> which means return FALSE, for all other cases, we need to go through
> those normal checks below.
I was just about to submit the same patch myself; my testsuite run
finished last night. This testsuite run was with a toolchain configured
"--with-arch=armv8-a --with-fpu=neon-fp-armv8 --with-float=hard
--with-mode=thumb --enable-languages=c,c++". I see 10 fewer unexpected
failures on the gcc testsuite with the patch, and no changes to the
other testsuite results.
Jim
next prev parent reply other threads:[~2015-11-04 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 9:45 Jiong Wang
2015-11-04 22:39 ` Jim Wilson [this message]
2015-11-11 12:09 ` Jiong Wang
2015-11-11 12:21 ` Ramana Radhakrishnan
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=563A88FE.7050409@linaro.org \
--to=jim.wilson@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiong.wang@foss.arm.com \
--cc=kyrylo.tkachov@arm.com \
--cc=ramana.radhakrishnan@foss.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).