From: James Greenhalgh <james.greenhalgh@arm.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: <gcc-patches@gcc.gnu.org>, <nd@arm.com>
Subject: Re: [Patch ARM/AArch64 03/11] AdvSIMD tests: be more verbose.
Date: Fri, 13 May 2016 14:03:00 -0000 [thread overview]
Message-ID: <20160513140303.GE11846@arm.com> (raw)
In-Reply-To: <1462973041-7911-4-git-send-email-christophe.lyon@linaro.org>
On Wed, May 11, 2016 at 03:23:53PM +0200, Christophe Lyon wrote:
> It is useful to have more detailed information in the logs when checking
> validation results: instead of repeating the intrinsic name, we now print
> its return type too.
>
> 2016-05-02 Christophe Lyon <christophe.lyon@linaro.org>
>
> * gcc.target/aarch64/advsimd-intrinsics/arm-neon-ref.h (CHECK,
> CHECK_FP, CHECK_CUMULATIVE_SAT): Print which type was checked.
OK.
Thanks,
James
next prev parent reply other threads:[~2016-05-13 14:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 13:24 [Patch ARM/AArch64 00/11][testsuite] AdvSIMD intrinsics update Christophe Lyon
2016-05-11 13:24 ` [Patch ARM/AArch64 08/11] Add missing vstX_lane fp16 tests Christophe Lyon
2016-05-13 14:53 ` James Greenhalgh
2016-05-19 16:20 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 06/11] Add missing vtst_p8 and vtstq_p8 tests Christophe Lyon
2016-05-13 14:37 ` James Greenhalgh
2016-05-13 14:41 ` Christophe Lyon
2016-05-13 14:48 ` James Greenhalgh
2016-05-19 11:54 ` Christophe Lyon
2016-05-20 13:49 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 09/11] Add missing vrnd{,a,m,n,p,x} tests Christophe Lyon
2016-05-12 8:45 ` Jiong Wang
2016-05-12 12:56 ` Christophe Lyon
2016-05-13 8:39 ` Jiong Wang
2016-05-13 14:56 ` James Greenhalgh
2016-05-19 16:22 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 01/11] Fix typo in vreinterpret.c test comment Christophe Lyon
2016-05-13 13:53 ` James Greenhalgh
2016-05-16 13:25 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 05/11] Add missing vreinterpretq_p{8,16} tests Christophe Lyon
2016-05-13 14:15 ` James Greenhalgh
2016-05-16 13:31 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 03/11] AdvSIMD tests: be more verbose Christophe Lyon
2016-05-13 14:03 ` James Greenhalgh [this message]
2016-05-16 13:26 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 02/11] We can remove useless #ifdefs from these tests: vmul, vshl and vtst Christophe Lyon
2016-05-13 13:56 ` James Greenhalgh
2016-05-16 13:25 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 10/11] Add missing tests for intrinsics operating on poly64 and poly128 types Christophe Lyon
2016-05-13 15:16 ` James Greenhalgh
2016-05-19 16:23 ` Kyrill Tkachov
2016-05-23 9:12 ` Christophe Lyon
2016-05-11 13:24 ` [Patch ARM/AArch64 07/11] Add missing vget_lane fp16 tests Christophe Lyon
2016-05-13 14:38 ` James Greenhalgh
2016-05-16 13:41 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 11/11] Add missing tests for vreinterpret, operating of fp16 type Christophe Lyon
2016-05-13 15:17 ` James Greenhalgh
2016-05-19 16:24 ` Kyrill Tkachov
2016-05-11 13:24 ` [Patch ARM/AArch64 04/11] Add forgotten vsliq_n_u64 test Christophe Lyon
2016-05-13 14:09 ` James Greenhalgh
2016-05-13 14:22 ` Christophe Lyon
2016-05-16 13:27 ` Kyrill Tkachov
2016-05-13 15:32 ` [Patch ARM/AArch64 00/11][testsuite] AdvSIMD intrinsics update James Greenhalgh
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=20160513140303.GE11846@arm.com \
--to=james.greenhalgh@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).