Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Analyze: Velop Mail Shield v0.0.3 Date: Fri, 5 Sep 2003 19:13:44 -0300 (BRT) From: =?ISO-8859-1?Q?Fr=E9d=E9ric_L=2E_W=2E_Meunier?= <0 AT pervalidus DOT tk> X-X-Sender: fredlwm AT pervalidus DOT dyndns DOT org To: cygwin AT cygwin DOT com Subject: Re: Binaries compiled with GCC 3.2-3 much bigger than with 2.95.3-10? In-Reply-To: Message-ID: References: X-Archive: encrypt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Answering 2 in 1. On Fri, 5 Sep 2003, Wayne wrote: > There have been discussions on various forums about increased > executable size and in particular, compile time, pretty much > since gcc-3.1 was in beta. Exe will be bigger than 2-95, even > after stripping. I agree that even on Linux this is usually the case, but not with lndir. 3.2.3 and 3.3.1 produced smaller binaries, while 3.2-3 doubled the size on Cygwin. Lapo Luchini wrote: > Did you "strip" the executable produced? AFAIK gcc3 has much > more "debug" infos, but once stripped should be of a similiar > size. Yes, and I also used strip on Cygwin to see it -Wl,-s was really working. The Makefile is like: CC = gcc CFLAGS = -O2 -pipe -Wall LDFLAGS = -Wl,-s INCLUDE = -I. all: lndir lndir: $(CC) $(CFLAGS) $(INCLUDE) -o lndir $(LDFLAGS) lndir.c I just did $ make $ make LDFLAGS= $ make CFLAGS='-Os -pipe -Wall' $ make CFLAGS='-Os -pipe -Wall' LDFLAGS= $ make CC=gcc-2 and so on. Anyway, I'll later compile other things to see it the size changes that much. I was just impressed by the difference since 3.2-3 on Cygwin is supposed to work like 3.x on Linux, or not ? -- How to contact me - http://www.pervalidus.net/contact.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/