From: Yaroslav K. <kav...@je...> - 2006-06-16 08:47:45
|
I build clisp from CVS head on mingw - it's ok. But size of lisp.exe has very much increased: from ~2400K (original 2.38) to ~6200K! I built clisp last time more than month back (or later). What is it? -- WBR, Yaroslav Kavenchuk. |
From: Sam S. <sd...@po...> - 2006-06-16 12:47:42
|
> * Yaroslav Kavenchuk <xnirapuhx@wragl.ol> [2006-06-16 11:49:37 +0300]: > > I build clisp from CVS head on mingw - it's ok. > > But size of lisp.exe has very much increased: > from ~2400K (original 2.38) to ~6200K! I think you are comparing the regular build with a debug one. -- Sam Steingold (http://www.podval.org/~sds) on Fedora Core release 5 (Bordeaux) http://camera.org http://jihadwatch.org http://mideasttruth.com http://memri.org http://iris.org.il http://thereligionofpeace.com War doesn't determine who's right, just who's left. |
From: Yaroslav K. <kav...@je...> - 2006-06-16 13:17:05
|
Sam Steingold wrote: >> I build clisp from CVS head on mingw - it's ok. >> >> But size of lisp.exe has very much increased: >> from ~2400K (original 2.38) to ~6200K! > > I think you are comparing the regular build with a debug one. Hmm, I do not use flag --with-debug. $ lisp.exe -M lispinit.mem --version GNU CLISP 2.38 (2006-01-24) (built on home [127.0.0.1]) Software: GNU C 3.4.5 (mingw special) gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -O2 -fexpensive-optimizations -falign-functions=4 -D_WIN32 -DUNICODE -DDYNAMIC_FFI -I. -x none -lintl libcharset.a libavcall.a libcallback.a /usr/local/lib/libreadline.a -ltermcap -luser32 -lws2_32 -lole32 -loleaut32 -luuid /usr/local/lib/libiconv.a -L/usr/local/lib -lsigsegv SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.3 libiconv 1.8 libreadline 5.0 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 WIN32) C Modules: (clisp i18n syscalls regexp readline) Installation directory: .\ User language: ENGLISH Machine: PC/386 (PC/?86) stnt067 [192.168.0.1] -- WBR, Yaroslav Kavenchuk. |
From: Sam S. <sd...@po...> - 2006-06-16 14:14:00
|
> * Yaroslav Kavenchuk <xnirapuhx@wragl.ol> [2006-06-16 16:19:09 +0300]: > > Sam Steingold wrote: >>> I build clisp from CVS head on mingw - it's ok. >>> >>> But size of lisp.exe has very much increased: >>> from ~2400K (original 2.38) to ~6200K! >> >> I think you are comparing the regular build with a debug one. > > Hmm, I do not use flag --with-debug. > > $ lisp.exe -M lispinit.mem --version > GNU CLISP 2.38 (2006-01-24) (built on home [127.0.0.1]) > Software: GNU C 3.4.5 (mingw special) > gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit ^^ this is what I meant. this means that the executable lisp.run contains the debugging information for gdb. there is no harm here: it does not run slower, and it does not take more ram, so, unless the extra 4M of disk space is critical for you, you can just leave it as is. I think this is the case since this patch: 2006-05-10 Bruno Haible <br...@cl...> * makemake.in: Respect the value of the environment variable CFLAGS given at configure time. it prepends the "default" CFLAGS to the CLISP CFLAGS, and the default CFLAGS for gcc is "-g -O2" > -Wreturn-type -Wmissing-declarations -Wno-sign-compare -O2 > -fexpensive-optimizations -falign-functions=4 -D_WIN32 -DUNICODE > -DDYNAMIC_FFI -I. -x none -lintl libcharset.a libavcall.a libcallback.a > /usr/local/lib/libreadline.a -ltermcap -luser32 -lws2_32 -lole32 > -loleaut32 -luuid /usr/local/lib/libiconv.a -L/usr/local/lib -lsigsegv > SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS > SPVW_MIXED TRIVIALMAP_MEMORY > libsigsegv 2.3 > libiconv 1.8 > libreadline 5.0 > Features: > (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL > COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS > LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 > WIN32) > C Modules: (clisp i18n syscalls regexp readline) > Installation directory: .\ > User language: ENGLISH > Machine: PC/386 (PC/?86) stnt067 [192.168.0.1] -- Sam Steingold (http://www.podval.org/~sds) on Fedora Core release 5 (Bordeaux) http://palestinefacts.org http://dhimmi.com http://openvotingconsortium.org http://jihadwatch.org http://memri.org http://thereligionofpeace.com The only time you have too much fuel is when you're on fire. |
From: Reini U. <ru...@x-...> - 2006-06-19 13:41:22
|
2006/6/16, Sam Steingold <sd...@po...>: > > * Yaroslav Kavenchuk <xnirapuhx@wragl.ol> [2006-06-16 16:19:09 +0300]: > > > > Sam Steingold wrote: > >>> I build clisp from CVS head on mingw - it's ok. > >>> > >>> But size of lisp.exe has very much increased: > >>> from ~2400K (original 2.38) to ~6200K! > >> > >> I think you are comparing the regular build with a debug one. > > > > Hmm, I do not use flag --with-debug. > > > > $ lisp.exe -M lispinit.mem --version > > GNU CLISP 2.38 (2006-01-24) (built on home [127.0.0.1]) > > Software: GNU C 3.4.5 (mingw special) > > gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit > ^^ > this is what I meant. > this means that the executable lisp.run contains the debugging > information for gdb. > there is no harm here: it does not run slower, and it does not take more > ram, so, unless the extra 4M of disk space is critical for you, you can > just leave it as is. strip lisp.exe will remove the debugging info included with -g. but it's not recommended for homemade builds |
From: Sam S. <sd...@po...> - 2006-06-19 13:50:04
|
> * Reini Urban <eh...@k-...> [2006-06-19 15:41:19 +0200]: > > 2006/6/16, Sam Steingold <sd...@po...>: >> > * Yaroslav Kavenchuk <xnirapuhx@wragl.ol> [2006-06-16 16:19:09 +0300]: >> > >> > Sam Steingold wrote: >> >>> I build clisp from CVS head on mingw - it's ok. >> >>> >> >>> But size of lisp.exe has very much increased: >> >>> from ~2400K (original 2.38) to ~6200K! >> >> >> >> I think you are comparing the regular build with a debug one. >> > >> > Hmm, I do not use flag --with-debug. >> > >> > $ lisp.exe -M lispinit.mem --version >> > GNU CLISP 2.38 (2006-01-24) (built on home [127.0.0.1]) >> > Software: GNU C 3.4.5 (mingw special) >> > gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit >> ^^ >> this is what I meant. >> this means that the executable lisp.run contains the debugging >> information for gdb. >> there is no harm here: it does not run slower, and it does not take more >> ram, so, unless the extra 4M of disk space is critical for you, you can >> just leave it as is. > > strip lisp.exe will remove the debugging info included with -g. > but it's not recommended for homemade builds strip will break (disassemble 'car) it may also interfere with executable images. -- Sam Steingold (http://www.podval.org/~sds) on Fedora Core release 5 (Bordeaux) http://thereligionofpeace.com http://truepeace.org http://jihadwatch.org http://camera.org http://honestreporting.com http://openvotingconsortium.org The only thing worse than X Windows: (X Windows) - X |