AW: next nightly build problem
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <a5ed692f8ab045d99f3f075abef60c56@HE104834.emea1.cds.t-internal.com> |
Hi, Don Cohen wrote: [3]> (software-type) "gcc -m64 -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -fno-strict-aliasing -ggdb -O0 -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DENABLE_UNICODE -DNO_TERMCAP_NCURSES -DDYNAMIC_FFI -DDYNAMIC_MODULES libgnu.a -ldl /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a /usr/local/lib64/libsigsegv.a -lc SAFETY=3 TYPECODES WIDE_HARD SPVW_BLOCKS SPVW_PURE SINGLEMAP_MEMORY libsigsegv 2.10 libffcall 1.13" Good point! Here's my MS-VC version (32 bit) for comparison. [13]> (software-type) "cl -G5 -Ot -Oy -Ob1 -Gs -Gf -Gy -Og -W4 -DUNICODE -DDYNAMIC_FFI -DNO_GETTEXT -I. charset.lib avcall.lib callback.lib user32.lib ws2_32.lib advapi32.lib ole32.lib shell32.lib sigsegv.lib SAFETY=1 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2" As you can see, all memory options are almost opposite. Regards, Jörg ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel