Hi!
Ping.
Grüße
Thomas
On 2022-11-25T12:09:36+0100, I wrote:
> Hi!
>
> Ping.
>
>
> Grüße
> Thomas
>
>
> On 2022-11-08T21:29:49+0100, I wrote:
>> Hi!
>>
>> On 2017-06-09T16:24:30+0200, Tom de Vries <tom_devr...@mentor.com> wrote:
>>> The patch defines an effective target stack_size, which is used in
>>> individual test-cases to add -DSTACK_SIZE=<value> [...]
>>
>>> gccint.info (edited for long lines):
>>> ...
>>> 7.2.3.12 Other attributes
>>> .........................
>>>
>>> 'stack_size'
>>> Target has limited stack size. [...]
>>
>> On top of that, OK to push the attached
>> "nvptx: stack size limits are relevant for execution only"?
>>
>>
>> Grüße
>> Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht
München, HRB 106955
>From 158a077129cb1579b93ddf440a5bb60b457e4b7c Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tho...@codesourcery.com>
Date: Tue, 8 Nov 2022 12:10:03 +0100
Subject: [PATCH] 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.
---
gcc/doc/sourcebuild.texi | 4 ++++
gcc/testsuite/lib/target-supports.exp | 16 ++++++++++++++++
2 files changed, 20 insertions(+)
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index 137f00aadc1f..5bbf6fc55909 100644
--- a/gcc/doc/sourcebuild.texi
+++ b/gcc/doc/sourcebuild.texi
@@ -2848,6 +2848,10 @@ Target has limited stack size. The stack size limit can be obtained using the
STACK_SIZE macro defined by @ref{stack_size_ao,,@code{dg-add-options} feature
@code{stack_size}}.
+Note that for certain targets, stack size limits are relevant for
+execution only, and therefore considered only if @code{dg-do run} is
+in effect, otherwise unlimited.
+
@item static
Target supports @option{-static}.
diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 750897d08548..39ed1723b03a 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -625,6 +625,22 @@ proc check_effective_target_trampolines { } {
# Return 1 if target has limited stack size.
proc check_effective_target_stack_size { } {
+ # For nvptx target, stack size limits are relevant for execution only.
+ if { [istarget nvptx-*-*] } {
+ # Find 'dg-do-what' in an outer frame.
+ set level 1
+ while true {
+ upvar $level dg-do-what dg-do-what
+ if [info exists dg-do-what] then break
+ incr level
+ }
+ verbose "check_effective_target_stack_size: found dg-do-what at level $level" 2
+
+ if { ![string equal [lindex ${dg-do-what} 0] run] } {
+ return 0
+ }
+ }
+
if [target_info exists gcc,stack_size] {
return 1
}
--
2.35.1
