[PING^3] nvptx: stack size limits are relevant for execution only (was: [PATCH, testsuite] Add effective target stack_size)

Hi! Ping. Grüße Thomas On 2022-12-20T08:55:08+0100, I wrote: > 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

[PING^2] nvptx: stack size limits are relevant for execution only (was: [PATCH, testsuite] Add effective target stack_size)

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 wrote: >>> The patch defines an effective target stack_size, which is used in >>> individual

[PING] nvptx: stack size limits are relevant for execution only (was: [PATCH, testsuite] Add effective target stack_size)

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 wrote: >> The patch defines an effective target stack_size, which is used in >> individual test-cases to add -DSTACK_SIZE= [...] > >> gccint.info (edited for long lines): >> ...

nvptx: stack size limits are relevant for execution only (was: [PATCH, testsuite] Add effective target stack_size)

Hi! On 2017-06-09T16:24:30+0200, Tom de Vries wrote: > The patch defines an effective target stack_size, which is used in > individual test-cases to add -DSTACK_SIZE= [...] > gccint.info (edited for long lines): > ... > 7.2.3.12 Other attributes > . > > 'stack_size' >

Re: [PATCH, testsuite] Add effective target stack_size

On Fri, Jun 09, 2017 at 04:24:30PM +0200, Tom de Vries wrote: > * gcc.dg/tree-prof/comp-goto-1.c: Same. > * gcc.dg/tree-prof/pr44777.c: Same. > --- a/gcc/testsuite/gcc.dg/tree-prof/comp-goto-1.c > +++ b/gcc/testsuite/gcc.dg/tree-prof/comp-goto-1.c > @@ -1,6 +1,8 @@ > /* {

Re: [PATCH, testsuite] Add effective target stack_size

On Jun 19, 2017, at 2:21 AM, Christophe Lyon wrote: > > The attached patch removes the support for STACK_SIZE in the testcase > as you suggested, and it works fine (cross-tested on aarch64/arm targets) > > OK for trunk? Ok.

Re: [PATCH, testsuite] Add effective target stack_size

On 12 June 2017 at 16:28, Tom de Vries wrote: > On 06/12/2017 02:28 PM, Christophe Lyon wrote: >> >> Hi Tom, >> >> On 9 June 2017 at 17:25, Mike Stump wrote: >>> >>> On Jun 9, 2017, at 7:24 AM, Tom de Vries wrote:

Re: [PATCH, testsuite] Add effective target stack_size

On 06/12/2017 02:28 PM, Christophe Lyon wrote: Hi Tom, On 9 June 2017 at 17:25, Mike Stump wrote: On Jun 9, 2017, at 7:24 AM, Tom de Vries wrote: this patch adds effective target stack_size. OK for trunk if x86_64 and nvptx testing succeeds?

Re: [PATCH, testsuite] Add effective target stack_size

Hi Tom, On 9 June 2017 at 17:25, Mike Stump wrote: > On Jun 9, 2017, at 7:24 AM, Tom de Vries wrote: >> this patch adds effective target stack_size. > >> OK for trunk if x86_64 and nvptx testing succeeds? > > Ok. > > The only last issue in this

Re: [PATCH, testsuite] Add effective target stack_size

On Jun 9, 2017, at 7:24 AM, Tom de Vries wrote: > this patch adds effective target stack_size. > OK for trunk if x86_64 and nvptx testing succeeds? Ok. The only last issue in this area that I know about is that there are a few more test cases that need up to 48 MB to

[PATCH, testsuite] Add effective target stack_size

Hi, this patch adds effective target stack_size. Atm, -DSTACK_SIZE= is defined at top-level in gcc_target_compile resulting in the macro being passed down to ~30k compilations. The macro is used in just 37 testcases. The patch defines an effective target stack_size, which is used in