------- Comment #4 from joseph at codesourcery dot com 2009-03-11 22:43 ------- Subject: Re: gcc.target/arm/neon/neon.exp tests for vmov fail on arm-linux-eabi
On Wed, 11 Mar 2009, jules at gcc dot gnu dot org wrote: > These failures show up because the tests are kind of weak. There's no > particular reason that vget_low* intrinsics should generate vmov instructions > as the tests are expecting: the assembly output shown with vldr/fstd works > just > as well, and no instructions at all (i.e. just a hint to the register > allocator) would work even better. That's the move intrinsic tests. I think polytypes.c is because of additional diagnostics added at some point for which target-independent tests were updated but not all target-specific tests (i.e., the testcase needs updating for the current front-end diagnostics). Unlike the move instrinsics tests polytypes.c is not an automatically generated file, so should be straightforward for anyone to fix. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38697
