Date:	Thu, 2 Jan 2003 07:50:32 +0000 (GMT)
From:	andris AT hal DOT astr DOT lu DOT lv
X-X-Sender:	andris AT laser4 DOT metsahovi DOT fgi DOT fi
To:	ams AT ludd DOT luth DOT se
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: stubify
In-Reply-To:	<200212311450.gBVEorP17093@speedy.ludd.luth.se>
Message-ID:	<Pine.LNX.4.50.0301020746190.18498-100000@laser4.metsahovi.fgi.fi>
References:	<200212311450 DOT gBVEorP17093 AT speedy DOT ludd DOT luth DOT se>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 31 Dec 2002 ams AT ludd DOT luth DOT se wrote:

> According to Richard Dawe:
> > ams AT ludd DOT luth DOT se wrote:
> > [snip]
> > > Remember I talked about a stack size option to stubify? I've added
> > > code to get an environment variable's value to choose the stack
> > > size. This way those that do want a big stack size can set it and it
> > > won't affect us that doesn't want it, except when we run programs
> > > somebody else built. (Or possibly the other way round.)
> >
> > How about a command-line argument to set stack size? Then people/we can modify
> > the gcc specs file to increase the stack size for all their programs, if they
> > want.
>
> Yes, that was my(?) original idea. However I concluded that messing
> with the spec file with it's somewhat cumbersome syntax wouldn't do
> anyone a service. Setting an environment variable is much safer.
>

I thought sometimes about using stubedit and putting support of setting
stack size from GCC command line (Simply I needed less modifications for
stubedit rather than for stubify). Of course possibility to use stubify
for that is better. In this case we could provide support for something like
	-stack=1024K
in GCC command line (one can easily specify it in LDFLAGS in Makefile)
for next updates of DJGPP port of GCC

Andris

- Raw text -