diff options
author | Tom de Vries <tdevries@suse.de> | 2020-09-24 10:03:10 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2020-09-24 10:15:37 +0200 |
commit | 7e437162001f258c8db4eae25da3bca812dd557a (patch) | |
tree | 59e411a3cf563f64505c6c3d792ce2d903a422e6 /gcc/tree-ssa-loop-ch.c | |
parent | c9da53d6987af5f8ff68b58dd76a9fbc900a6a21 (diff) | |
download | gcc-7e437162001f258c8db4eae25da3bca812dd557a.zip gcc-7e437162001f258c8db4eae25da3bca812dd557a.tar.gz gcc-7e437162001f258c8db4eae25da3bca812dd557a.tar.bz2 |
[testsuite] Require non_strict_align in pr94600-{1,3}.c
With the nvptx target, we run into:
...
FAIL: gcc.dg/pr94600-1.c scan-rtl-dump-times final "\\(mem/v" 6
FAIL: gcc.dg/pr94600-1.c scan-rtl-dump-times final "\\(set \\(mem/v" 6
FAIL: gcc.dg/pr94600-3.c scan-rtl-dump-times final "\\(mem/v" 1
FAIL: gcc.dg/pr94600-3.c scan-rtl-dump-times final "\\(set \\(mem/v" 1
...
The scans attempt to check for volatile stores, but on nvptx we have memcpy
instead.
This is due to nvptx being a STRICT_ALIGNMENT target, which has the effect
that the TYPE_MODE for the store target is set to BKLmode in
compute_record_mode.
Fix the FAILs by requiring effective target non_strict_align.
Tested on nvptx.
gcc/testsuite/ChangeLog:
2020-09-24 Tom de Vries <tdevries@suse.de>
* gcc.dg/pr94600-1.c: Require effective target non_strict_align for
scan-rtl-dump-times.
* gcc.dg/pr94600-3.c: Same.
Diffstat (limited to 'gcc/tree-ssa-loop-ch.c')
0 files changed, 0 insertions, 0 deletions