From: Mike Stump <mikestump@comcast.net>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Ramana Radhakrishnan <ramrad01@arm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch ARM/testsuite 00/22] Neon intrinsics executable tests
Date: Thu, 12 Jun 2014 16:45:00 -0000 [thread overview]
Message-ID: <51D0E62F-AA01-40EB-AB73-FE3DEDD98577@comcast.net> (raw)
In-Reply-To: <CAKdteOYmNA4Tn-8Ce1shg=h7HHMb6wWpSBW7t8zgFRCesevgew@mail.gmail.com>
On Jun 12, 2014, at 7:26 AM, Christophe Lyon <christophe.lyon@linaro.org> wrote:
> On 12 June 2014 04:31, Mike Stump <mikestump@comcast.net> wrote:
>> On Jun 10, 2014, at 3:03 PM, Ramana Radhakrishnan <ramana.gcc@googlemail.com> wrote:
>>> At this point I'm going to wait to see if any of the testsuite
>>> maintainers step in and comment
>>
>> [ ducks ] So, I wasn’t going to comment… If you guys do something really stupid, I’ll scream, as hopefully will others. Doing something a little misguided I don’t think hurts much. The worst case if you figure out in a year or two why it was a bad idea and then fix it, not the end of the world.
>
> If the execution part is OK and the scan-assembler is questionable, I
> can just remove that part (or leave it commented until we decide
> otherwise).
Don’t read my comment as stating scanning as being questionable. In fact, scanning is slightly better as one can see the results on a cross easier and faster… for example when someone wants to study a regression they caused and they don’t have the target, they can build to cc1 and then run the test case by hand and see what the scan issues are. If it where an executable test case, they would have to puzzle why the test case is different and understand what they are reading (they might not be familiar with the target).
next prev parent reply other threads:[~2014-06-12 16:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 22:04 Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 01/22] Neon intrinsics execution tests initial framework Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 02/22] Add unary operators: vabs and vneg Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 03/22] Add binary operators: vadd, vand, vbic, veor, vorn, vorr, vsub Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 04/22] Add comparison operators: vceq, vcge, vcgt, vcle and vclt Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 05/22] Add comparison operators with floating-point operands: vcage, vcagt, vcale and cvalt Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 06/22] Add unary saturating operators: vqabs and vqneg Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 07/22] Add binary saturating operators: vqadd, vqsub Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 08/22] Add vabal tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 09/22] Add vabd tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 10/22] Add vabdl tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 11/22] Add vaddhn tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 12/22] Add vaddl tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 13/22] Add vaddw tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 14/22] Add vbsl tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 15/22] Add vclz tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 16/22] Add vdup and vmov tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 17/22] Add vld1_dup tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 18/22] Add vld2/vld3/vld4 tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 19/22] Add vld2_lane, vld3_lane and vld4_lane tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 20/22] Add vmul tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 21/22] Add vshl tests Christophe Lyon
2014-06-05 22:05 ` [Patch ARM/testsuite 22/22] Add vuzp and vzip tests Christophe Lyon
2014-06-27 12:55 ` [Patch ARM/testsuite 03/22] Add binary operators: vadd, vand, vbic, veor, vorn, vorr, vsub Ramana Radhakrishnan
2014-06-27 13:15 ` Christophe Lyon
2014-06-30 8:03 ` Ramana Radhakrishnan
2014-06-30 10:59 ` Marcus Shawcroft
2014-06-27 12:52 ` [Patch ARM/testsuite 02/22] Add unary operators: vabs and vneg Ramana Radhakrishnan
2014-06-27 13:04 ` Christophe Lyon
2014-06-27 13:18 ` Christophe Lyon
2014-06-27 7:56 ` [Patch ARM/testsuite 01/22] Neon intrinsics execution tests initial framework Ramana Radhakrishnan
2014-06-30 13:11 ` Christophe Lyon
2014-06-05 23:33 ` [Patch ARM/testsuite 00/22] Neon intrinsics executable tests Joseph S. Myers
2014-06-06 14:40 ` Christophe Lyon
2014-06-06 15:57 ` Ramana Radhakrishnan
2014-06-06 20:15 ` Christophe Lyon
2014-06-11 13:30 ` Christophe Lyon
2014-06-10 22:03 ` Ramana Radhakrishnan
2014-06-11 13:31 ` Christophe Lyon
2014-06-12 2:32 ` Mike Stump
2014-06-12 14:26 ` Christophe Lyon
2014-06-12 16:45 ` Mike Stump [this message]
2014-06-23 14:42 ` Christophe Lyon
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=51D0E62F-AA01-40EB-AB73-FE3DEDD98577@comcast.net \
--to=mikestump@comcast.net \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramrad01@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).