Should the prologue code be rewritten to have a thread created before main() is called?
Also, it'd be interesting to see where are the new thread stacks are created, I've looked at how other OSes do that, and they just simply create a new segment. Since m$ seem to not give you stack segment for the stack completely, it should allocate thread stacks somewhere in that stack segment. On Mon, Jun 8, 2009 at 6:06 PM, Johnny Willemsen <jwillem...@remedy.nl> wrote: > Hi, > >> gcc code may user more of the stack than whatever code that msvc >> produces, thus >> dipping into the red zone more often. So far, I don't see how the 64k >> limit of the >> stack on the main thread can be avoided at all.. > > The only option I see (which also Danny proposed) is to create a worker > thread, use that as main thread, then we can control the stack size. > > I will rewrite a few tests at our side to get some objects from the heap > instead of from the stack. > > Johnny > > ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
