Re: FWD: gcc in debian/unstable
Are you sure he doesn't mean --enable-checking? --enable-debug should
not affect compile time significantly.
On Fri, Oct 31, 2003 at 08:44:49PM -0800, Randolph Chung wrote:
> FYI -randolph
>
> ----- Forwarded message from David Mosberger <davidm@napali.hpl.hp.com> -----
>
> From: David Mosberger <davidm@napali.hpl.hp.com>
> Date: Fri, 31 Oct 2003 15:20:36 -0800
> To: debian-ia64@lists.debian.org
> Subject: gcc in debian/unstable
> Reply-To: davidm@hpl.hp.com
> X-Mailing-List: <debian-ia64@lists.debian.org> archive/latest/1242
>
> While looking for something else, I noticed that the GCC in
> Debian/unstable is configured with --enable-debug:
>
> $ gcc -v
> Reading specs from /usr/lib/gcc-lib/ia64-linux/3.3.2/specs
> Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc ia64-linux
> Thread model: posix
> gcc version 3.3.2 20031005 (Debian prerelease)
>
> Is this intentional? A while back, I measured this with gcc-pre3.4
> and with that compiler, the overhead of --enable-debug was >30%.
> Unless there are good reasons for it, my recommendation would be to
> build with --disable-debug, as that would likely speed up
> compile-times a lot.
>
> --david
>
>
> --
> To UNSUBSCRIBE, email to debian-ia64-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
> ----- End forwarded message -----
>
>
> --
> To UNSUBSCRIBE, email to debian-gcc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
Reply to: