On 14 June 2017 at 16:27, Richard Earnshaw (lists) <richard.earns...@arm.com> wrote: > On 13/06/17 18:29, Richard Earnshaw (lists) wrote: >> This test was overriding the options that had been detected as being >> necessary to enable Neon. The result was that the combination of the >> test's options and those auto-detected were not compatible with neon >> leading to a test failure. The correct fix here is to stick with the >> options that dg-add-options arm_neon has worked out. >> >> * gcc.target/arm/neon-thumb2-move.c (dg-options): Don't override >> the architecture options added by dg-add-options arm_neon. >> >> > > The thumb2-slow-flash-data tests were relying (incorrectly) on a > particular FPU being enabled by default. These tests are fixed by > adding +fp to the architecture selected. > > * gcc.target/arm/neon-thumb2-move.c (dg-options): Don't override > the architecture options added by dg-add-options arm_neon. > * gcc.target/arm/thumb2-slow-flash-data-2.c (dg-opitions): Add +fp > to the architecture. > * gcc.target/arm/thumb3-slow-flash-data-3.c (dg-opitions): Likewise. > * gcc.target/arm/thumb4-slow-flash-data-3.c (dg-opitions): Likewise. > * gcc.target/arm/thumb5-slow-flash-data-3.c (dg-opitions): Likewise. >
I confirm they now pass on my side: http://people.linaro.org/~christophe.lyon/cross-validation/gcc-test-patches/248942-roll-up.patch2/report-build-info.html > > R.
