From: Alan Lawrence <alan.lawrence@arm.com>
To: Charles Baylis <charles.baylis@linaro.org>
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] [ARM] PR63870 improve error messages for NEON vldN_lane/vstN_lane
Date: Fri, 03 Jul 2015 13:01:00 -0000 [thread overview]
Message-ID: <5596879D.8000607@arm.com> (raw)
In-Reply-To: <1435851584-16430-1-git-send-email-charles.baylis@linaro.org>
Charles Baylis wrote:
> These patches are a port of the changes do the same thing for AArch64 (see
> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01984.html)
>
> The first patch ports over some infrastructure, and the second converts the
> vldN_lane and vstN_lane intrinsics. The changes required for vget_lane and
> vset_lane will be done in a future patch.
>
> The third patch includes the test cases from the AArch64 version, except that
> the xfails for arm targets have been removed. If this series gets approved
> before the AArch64 patch, I will commit the tests with xfail for aarch64
> targets.
Given the large number of test cases, essentially because of test framework
limitations, does it make sense to put these in their own directory? Just a thought.
Cheers, Alan
prev parent reply other threads:[~2015-07-03 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 15:40 Charles Baylis
2015-07-02 15:40 ` [PATCH 1/3] [ARM] PR63870 NEON error messages Charles Baylis
2015-07-06 10:18 ` Alan Lawrence
2015-07-07 12:30 ` Alan Lawrence
2015-07-07 19:03 ` Charles Baylis
2015-07-02 15:40 ` [PATCH 2/3] " Charles Baylis
2015-07-02 15:40 ` [PATCH 3/3] " Charles Baylis
2015-07-03 13:01 ` Alan Lawrence [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=5596879D.8000607@arm.com \
--to=alan.lawrence@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=charles.baylis@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
/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).