Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.2.0.9.2.20021224080405.00fff778@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Tue, 24 Dec 2002 08:16:59 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Re:Strange behaviour of gcc
In-Reply-To:	<3E00A20100008E83@mail-8.tiscalinet.it>
References:	<20021224051134 DOT 95173 DOT qmail AT web21408 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0

Fabrizio,

Now we're back to Max's question: Why does it matter to you?

Stack space is usually far more limited than heap space, which I assume is 
what motivates this behavior in the code generator. The programming 
language's semantics are maintained. And I challenge you to show a 
performance problem because some heap allocations are involved.

Randall Schulz


At 07:21 2002-12-24, fabrizio_ge-wolit AT tiscali DOT it wrote:

> >-- Messaggio Originale --
> >Date: Tue, 24 Dec 2002 16:11:34 +1100 (EST)
> >From: Danny Smith <danny_r_smith_2001 AT yahoo DOT co DOT nz>
> >Subject: Re:Strange behaviour of gcc
> >To: cygwin AT cygwin DOT com
> >Cc: fabrizio_ge-wolit AT tiscali DOT it
> >
> >
> >fabrizio_ge-wolit AT tiscali DOT it wrote:
> >> Is there a reason why the symbol __alloca appears?
> >
> >
> >GCC's __builtin_alloca uses a helper function called _alloca to check
> >the stack whenever allocating more that 4000  bytes in one go.
>
>Thanks a lot Danny. Is there a way to avoid that? I tried -fno-builtin,
>but it didn't seem to work (__alloca is still there).
>
>Fabrizio


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -