On Aug 17, 2008, at 10:46 AM, Hans Petter Egesund wrote:
Den 17. aug. 2008 kl. 16.41 skrev Christian Jaeger:
Hans Petter Egesund wrote:
I did a: time gsc -keep-c -expansion ssax-sxml > ! expansion.scm
Sorry, I was using tcsh, this will work just as well:
time gsc ssax-sxml
The -expansion options writes to stdout the scheme source with all macros expanded, all functions inlined, all specializations made, ..., and the exclamation point saves the redirect in expansion.scm even if expansion.scm already exists (I run my shell with noclobber set). The -keep-c option saves the C file. I wanted the expanded version and the C file to check that the changes I was making were actually being used.
On my machine, it took roughly 6.3GB of memory at one point for gcc to compiler the C file; it was this version of gcc:
frying-pan:~/programs/gambc-v4_2_3/ssax-sxml> gcc -v Using built-in specs. Target: x86_64-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c+ +,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with- system-zlib --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/ 4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx- debug --enable-objc-gc --enable-mpfr --enable-checking=release -- build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
my computer (64-bit ADM, 8GB ram, Ubuntu) is still trying to compile the file. It has been running for 6 hours or so, and is swapping a lot.
I don't know what else you have running; what does top tell you about the cc1 process (gcc's back end program).
Brad