On Fri, Jun 17, 2016 at 04:25:31PM +0200, Christophe Lyon wrote: > On 10 June 2016 at 14:29, James Greenhalgh <james.greenha...@arm.com> wrote: > > > > Hi, > > > > My autotester picked up some issues with the vcvt{ds}_n_* intrinsics > > added in r237200. > > > Hi, > > What tests does your autotester perform? I haven't noticed these > problems when running the GCC testsuite on the usual aarch64 > targets. I'm interested in increasing coverage, if doable.
Hi Christophe, I think we've spoken about this before [1], but the autotester is using an internal testsuite that is not feasible to share upstream. To see the sorts of tests that we're running, have a look at the LLVM testsuite. If the layout of the testsuite hasn't changed since I last looked, you should be able to find an example at: <llvm-testsuite>/SingleSource/UnitTests/Vector/AArch64/aarch64_neon_intrinsics.c Hope that helps, James [1]: https://gcc.gnu.org/ml/gcc-patches/2015-11/msg00775.html