diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2022-11-08 12:10:03 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2023-09-12 11:43:07 +0200 |
| commit | 56004123ab74193d88ad297877fa4e2a0d7ef5b1 (patch) | |
| tree | 0b7d45ccfbdfb8763f82db496672a6adc8ee2b5f /gcc/go | |
| parent | 949f1ccf1ba9d1f33ca3809424e97429b717950a (diff) | |
| download | gcc-56004123ab74193d88ad297877fa4e2a0d7ef5b1.zip gcc-56004123ab74193d88ad297877fa4e2a0d7ef5b1.tar.gz gcc-56004123ab74193d88ad297877fa4e2a0d7ef5b1.tar.bz2 | |
nvptx: stack size limits are relevant for execution only
For non-'dg-do run' test cases, that means: big 'dg-require-stack-size' need
not be UNSUPPORTED (and indeed now do all PASS), 'dg-add-options stack_size'
need not define (and thus limit) 'STACK_SIZE' (and still do all PASS).
Re "Find 'dg-do-what' in an outer frame", currently (sources not completely
clean, though), we've got:
$ git grep -F 'check_effective_target_stack_size: found dg-do-what at level ' -- build-gcc/\*.log | sort | uniq -c
6 build-gcc/gcc/testsuite/gcc/gcc.log:check_effective_target_stack_size: found dg-do-what at level 2
267 build-gcc/gcc/testsuite/gcc/gcc.log:check_effective_target_stack_size: found dg-do-what at level 3
239 build-gcc/gcc/testsuite/gcc/gcc.log:check_effective_target_stack_size: found dg-do-what at level 4
gcc/testsuite/
* lib/target-supports.exp (check_effective_target_stack_size): For
nvptx target, stack size limits are relevant for execution only.
gcc/
* doc/sourcebuild.texi (stack_size): Update.
Diffstat (limited to 'gcc/go')
0 files changed, 0 insertions, 0 deletions