Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <5.2.0.9.2.20021224080405.00fff778@pop3.cris.com> X-Sender: rrschulz@pop3.cris.com Date: Tue, 24 Dec 2002 08:16:59 -0800 To: cygwin@cygwin.com From: Randall R Schulz Subject: Re:Strange behaviour of gcc In-Reply-To: <3E00A20100008E83@mail-8.tiscalinet.it> References: <20021224051134.95173.qmail@web21408.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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@tiscali.it wrote: > >-- Messaggio Originale -- > >Date: Tue, 24 Dec 2002 16:11:34 +1100 (EST) > >From: Danny Smith > >Subject: Re:Strange behaviour of gcc > >To: cygwin@cygwin.com > >Cc: fabrizio_ge-wolit@tiscali.it > > > > > >fabrizio_ge-wolit@tiscali.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/