aboutsummaryrefslogtreecommitdiff
path: root/gcc/fortran/trans-openmp.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-08-11 18:20:17 +0200
committerTom de Vries <tdevries@suse.de>2020-08-12 14:04:41 +0200
commitfb9b3c0ff7d347934b364e3ab06d4cf56726df33 (patch)
treeec1acaec76a2b08cbdc686880ceeb5e73d44ea45 /gcc/fortran/trans-openmp.c
parentb9c7fe59f9f66ecc091e215c826ecd1a04d032dc (diff)
downloadgcc-fb9b3c0ff7d347934b364e3ab06d4cf56726df33.zip
gcc-fb9b3c0ff7d347934b364e3ab06d4cf56726df33.tar.gz
gcc-fb9b3c0ff7d347934b364e3ab06d4cf56726df33.tar.bz2
[testsuite] Add effective target large_initializer
When compiling builtin-object-size-21.c for nvptx, cc1 times out while emitting the initializer for global variable xm3_3. With x86_64, we are able to emit the initializer with a few lines of assembly: ... xm3_3: .byte 0 .zero 9223372036854775803 .byte 1 .byte 2 .byte 3 ... but with nvptx, we don't have some something similar available, and thus generate: ... .visible .global .align 1 .u32 xm3_3[2305843009213693952] = { 0, 0, 0, ... ... Introduce an effective target large_initializer, returning false for nvptx, and require it for test-cases with large initializers. Tested on nvptx with make check-gcc. gcc/testsuite/ChangeLog: PR testsuite/96566 * lib/target-supports.exp (check_effective_target_large_initializer): New proc. * gcc.dg/builtin-object-size-21.c: Require large_initializer. * gcc.dg/strlenopt-55.c: Same.
Diffstat (limited to 'gcc/fortran/trans-openmp.c')
0 files changed, 0 insertions, 0 deletions