public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>
Cc: Jim Wilson <jim.wilson@linaro.org>,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [ARM] neon-testgen.ml typo
Date: Fri, 30 Oct 2015 14:47:00 -0000	[thread overview]
Message-ID: <CAKdteOYbxkfwHHbuBC+sH_STGMKoipH7m3LFD9jM44D4Fn6Bfw@mail.gmail.com> (raw)
In-Reply-To: <56337FD6.5040602@foss.arm.com>

On 30 October 2015 at 15:33, Ramana Radhakrishnan
<ramana.radhakrishnan@foss.arm.com> wrote:
>
>
> On 29/10/15 17:23, Jim Wilson wrote:
>> I noticed a comment typo in this file while using grep to look for
>> other stuff.  The typo is easy to fix.
>>
>> I tried running neon-testgen.ml to verify, but it is apparently no
>> longer valid ocaml, as it doesn't work with the ocamlc 4.01.0 I have
>> on Ubuntu 14.04.  I get a syntax error.  Someone who knows ocaml will
>> have to fix this.  Meanwhile, the patch to fix the typo should still
>> be OK, as this is a separate problem.
>>
>> Jim
>>
>
> This is OK.
>
> I'd really like neon-testgen.ml and the tests in gcc.target/arm/neon to be removed if all the intrinsics are now tested from Christophe's work in getting his advsimd tests integrated. Where are we on that ?
>

The tests I added cover all ARMv7 intrinsics. I have converted all my tests.

There were a few additions to support some aarch64 specific intrinsics.

However, most of the tests in gcc.target/arm/neon contain scan-asm
directives which mine don't.
My tests do check functionality (they are executable, comparing their
results against expected values).

Christophe.

> regards
> Ramana

  reply	other threads:[~2015-10-30 14:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 17:29 Jim Wilson
2015-10-30 14:37 ` Ramana Radhakrishnan
2015-10-30 14:47   ` Christophe Lyon [this message]
2015-11-04 12:16     ` Ramana Radhakrishnan
2015-11-06 20:29       ` Christophe Lyon
2015-11-12 22:18         ` Christophe Lyon
2015-11-13 10:24           ` Christophe Lyon
2015-11-13 10:28             ` Kyrill Tkachov
2015-11-13 11:18             ` Ramana Radhakrishnan
2015-11-13 11:24               ` Kyrill Tkachov
2015-11-13 13:36                 ` Christophe Lyon
2015-11-24 15:25                   ` Christophe Lyon
2015-11-02 12:06 ` Julian Brown
2015-11-02 12:21   ` Kyrill Tkachov

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=CAKdteOYbxkfwHHbuBC+sH_STGMKoipH7m3LFD9jM44D4Fn6Bfw@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jim.wilson@linaro.org \
    --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).