Re: honoring gcc test stack size

2008-02-13 Thread Hans-Peter Nilsson
> Date: Wed, 13 Feb 2008 14:20:38 -0600 > From: Joel Sherrill <[EMAIL PROTECTED]> > Hans-Peter Nilsson wrote: > > but > > if so, it seems simplest to fake a simulator as: > > set_board_info sim false > > > > > I'll try that next. In case it wasn't clear: don't forget to use that in a generic

Re: honoring gcc test stack size

2008-02-13 Thread Joel Sherrill
Hans-Peter Nilsson wrote: Date: Wed, 13 Feb 2008 10:59:17 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> OK. I will add it to the GCC Projects page. Would this go into the Bug Patrol section of the Beginner Projects section? By the name of it, it sounds like it. I know they

Re: honoring gcc test stack size

2008-02-13 Thread Hans-Peter Nilsson
> From: "Dave Korn" <[EMAIL PROTECTED]> > Date: Wed, 13 Feb 2008 17:50:42 - > On 13 February 2008 16:36, Hans-Peter Nilsson wrote: > As a datapoint, the standard per-thread stack allocation on win32 platforms > is 2MB. That might make a more reasonable cutoff point, because in what's > prob

Re: honoring gcc test stack size

2008-02-13 Thread Hans-Peter Nilsson
> Date: Wed, 13 Feb 2008 10:59:17 -0600 > From: Joel Sherrill <[EMAIL PROTECTED]> > OK. I will add it to the GCC Projects page. > Would this go into the Bug Patrol section of the > Beginner Projects section? By the name of it, it sounds like it. I'm not sure a non-executable setup would make mu

RE: honoring gcc test stack size

2008-02-13 Thread Dave Korn
On 13 February 2008 16:36, Hans-Peter Nilsson wrote: >> Date: Wed, 13 Feb 2008 10:12:45 -0600 >> From: Joel Sherrill <[EMAIL PROTECTED]> > >> Would it make sense in the future as a (beginner?) >> GCC project to let me generate a set of GCC testresults >> and let someone see which tests have issue

Re: honoring gcc test stack size

2008-02-13 Thread Joel Sherrill
Hans-Peter Nilsson wrote: Date: Wed, 13 Feb 2008 10:12:45 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> Would it make sense in the future as a (beginner?) GCC project to let me generate a set of GCC testresults and let someone see which tests have issues honoring the stack size. (Run

Re: honoring gcc test stack size

2008-02-13 Thread Hans-Peter Nilsson
> Date: Wed, 13 Feb 2008 10:12:45 -0600 > From: Joel Sherrill <[EMAIL PROTECTED]> > Would it make sense in the future as a (beginner?) > GCC project to let me generate a set of GCC testresults > and let someone see which tests have issues honoring > the stack size. > > (Run 1) Run with a small 2-

Re: honoring gcc test stack size

2008-02-13 Thread Joel Sherrill
Joel Sherrill wrote: Hans-Peter Nilsson wrote: Date: Tue, 12 Feb 2008 15:47:14 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> I investigated one failure: pr20621-1.x3 You mean gcc/testsuite/gcc.c-torture/execute/pr20621-1.c at -O3? From the looks of it, it would take abo

Re: honoring gcc test stack size

2008-02-12 Thread Joel Sherrill
Hans-Peter Nilsson wrote: Date: Tue, 12 Feb 2008 15:47:14 -0600 From: Joel Sherrill <[EMAIL PROTECTED]> I investigated one failure: pr20621-1.x3 You mean gcc/testsuite/gcc.c-torture/execute/pr20621-1.c at -O3? From the looks of it, it would take about 2*0x4000*4 bytes stack.

Re: honoring gcc test stack size

2008-02-12 Thread Hans-Peter Nilsson
> Date: Tue, 12 Feb 2008 15:47:14 -0600 > From: Joel Sherrill <[EMAIL PROTECTED]> > I investigated one failure: pr20621-1.x3 You mean gcc/testsuite/gcc.c-torture/execute/pr20621-1.c at -O3? >From the looks of it, it would take about 2*0x4000*4 bytes stack. > and discovered that it is using a LOT