diff options
| author | Richard Earnshaw <rearnsha@arm.com> | 2017-06-16 21:07:20 +0000 |
|---|---|---|
| committer | Richard Earnshaw <rearnsha@gcc.gnu.org> | 2017-06-16 21:07:20 +0000 |
| commit | e3e266bfb1eb3e8c10f7461910529e0cb566343d (patch) | |
| tree | 6b81db7f9a5c77ae421c48b239f13b9bfa1edd54 /gcc/cp/lambda.c | |
| parent | 718a3eab2906217c70f27077446fa0e8ddb1bf7b (diff) | |
| download | gcc-e3e266bfb1eb3e8c10f7461910529e0cb566343d.zip gcc-e3e266bfb1eb3e8c10f7461910529e0cb566343d.tar.gz gcc-e3e266bfb1eb3e8c10f7461910529e0cb566343d.tar.bz2 | |
[arm] Fix various tests
The neon-thumb2-move.c 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.
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.
From-SVN: r249310
Diffstat (limited to 'gcc/cp/lambda.c')
0 files changed, 0 insertions, 0 deletions