This is the mail archive of the
mailing list for the Cygwin project.
Re: Strange behaviour of gcc
- From: fabrizio_ge-wolit at tiscali dot it
- To: "Max Bowsher" <maxb at ukf dot net>,cygwin at cygwin dot com
- Date: Sun, 29 Dec 2002 11:38:43 +0100
- Subject: Re: Strange behaviour of gcc
>-- Messaggio Originale --
>From: "Max Bowsher" <email@example.com>
>Subject: Re: Strange behaviour of gcc
>Date: Mon, 23 Dec 2002 23:25:00 -0000
>> Can somebody explain why gcc (version 3.2 20020927) on Cygwin does
>Yes. Gcc's optimizer chose to make a large amount of local variable
>allocation into an alloca call.
>Does it matter?
For what I'm trying to do, it does. I would like to build a DLL which is
not linked to the C runtime library in order to have a smaller file (a trick
copied from Winamp plug-ins), and I don't mind about sub-optimal performance.
The executable dlopen()s the DLL and provides some callbacks to it.
If the DLL is linked to CRT, it is 20KB long. If it is not, it is 8KB long
(but obviously it does not have alloca available).
Is there a gcc option to build code without the call to alloca?
Tiscali ADSL: abbonati entro il 31 gennaio.
Non paghi l'attivazione.
Non paghi il primo mese.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html