- Sep 25, 2011
-
-
Raymond Toy authored
entries with just the file path, removing the revision number, date, author and state. The actual information is now computed during compilation and stored in the fasl itself. (See ticket:48.)
-
- Sep 24, 2011
-
-
Raymond Toy authored
Make the size of all spaces configurable from the command line. code/commandline.lisp: o Define the switches so lisp doesn't complain. general-info/lisp.1: o Document new switches. general-info/release-20c.txt: o Update lisp/Darwin-os.c lisp/FreeBSD-os.c lisp/Linux-os.c lisp/NetBSD-os.c lisp/backtrace.c lisp/cgc.c lisp/gencgc.c lisp/os-common.c lisp/ppc-validate.h lisp/purify.c lisp/solaris-os.c lisp/sparc-arch.c lisp/sparc-validate.h lisp/x86-validate.h: lisp/validate.c o Basically rename CONTROL_STACK_SIZE, BINDING_STACK_SIZE, READ_ONLY_SPACE_SIZE, and STATIC_SPACE_SIZE to control_stack_size, binding_stack_size, read_only_space_size, and static_space_size, respectively. lisp/coreparse.c o Check the space size in the core file against the allocated size. If the allocated space is too small, print an error message and exit. lisp/globals.c o Define new variables for the allocated size of spaces. lisp/globals.h o Declare the new variables for the size of the spaces. lisp/lisp.c o Set the default values of the spaces. o Parse the new command-line flags and set the space sizes. lisp/sunos-os.c: o Added os_init0 (that we forgot last time). lisp/x86-assem.S: o Change $CONTROL_STACK_END to GNAME(control_stack_end) to get the correct end of the stack.
-
- Sep 03, 2011
-
-
rtoy authored
Bug was pointed by Christophe in private email. Fix is based on his suggested solution. Some examples that should work now: (round 100000000002.9d0) -> 100000000003 (round (+ most-positive-fixnum 1.5w0)) -> 536870912
-
- Sep 01, 2011
-
-
rtoy authored
-
- Aug 21, 2011
-
-
rtoy authored
Patch from Helmut Eller, cmucl-imp 2011-08-11.
-
- Jun 29, 2011
-
-
rtoy authored
stream.lisp: o Remove the old code that was the first attempt at fixing issue #43. This was wrong. fd-stream.lisp: o Fix issue #43. Even if we have a string-buffer, we need to take into account any octets in the in-buffer (if it exists) that have not been processed. This happens if the in-buffer does not have enough octets at the end to form a complete character for the given encoding. o Some debugging prints added, but disabled.
-
- Jun 27, 2011
-
-
rtoy authored
code/unidata.lisp: o Update unicode version to 6.0.0 o Add pointer to build-unidata.lisp. tools/build-unidata.lisp: o Update unicode version to 6.0.0 o Print out directory path so we can see where we're getting the data from. i18n/CaseFolding.txt i18n/CompositionExclusions.txt i18n/DerivedNormalizationProps.txt i18n/NameAliases.txt i18n/NormalizationCorrections.txt i18n/SpecialCasing.txt i18n/UnicodeData.txt i18n/WordBreakProperty.txt i18n/tests/NormalizationTest.txt i18n/tests/WordBreakTest.txt: o Update with new files from unicode.org.
-
rtoy authored
That changes causes the Unicode normalization and word-break tests to fail. I do not know why this causes the tests to fail, but it causes the test program to suck in the entire file into a string instead of just one line.
-
- Jun 10, 2011
-
-
rtoy authored
This makes it easy to make an executable image that doesn't need unidata.bin around. (Should we do this for normal cores? It seems to add about 1 MB to the core size.) code/unidata.lisp: o Add LOAD-ALL-UNICODE-DATA to load all unicode data. o Add UNICODE-DATA-LOADED-P to check that unicode data has been loaded. code/print.lisp: o If unicode data is loaded, don't check for existence of *unidata-path*, because we don't need it. code/exports.lisp: o Export LOAD-ALL-UNICODE-DATA. general-info/release-20c.txt: o Update info
-
- Jun 08, 2011
-
-
rtoy authored
This change need to support the new recommended way of loading asdf2 with require. This is a backward compatible change.
-
- May 31, 2011
-
-
rtoy authored
This change requires a cross-compile. Use boot-2011-04-01-cross.lisp as the cross-compile script. bootfiles/20b/boot-2011-04-01-cross.lisp: o New cross-compile bootstrap file lisp/lisp.c: o Recognize -unidata option and setup *UNIDATA-PATH* appropriately. code/commandline.lisp: o Add defswitch for unidata so we don't get complaints about unknown switch. code/unidata.lisp: o Rename +UNIDATA-PATH+ to *UNIDATA-PATH*, since it's not a constant anymore. o Update code to use new name. code/print.lisp: o Update code to use *UNIDATA-PATH* compiler/sparc/parms.lisp: o Add *UNIDATA-PATH* to list of static symbols. o Add back in spare-9 and spare-8 static symbols since we need to do a cross-compile for this change anyway. compiler/x86/parms.lisp: o Add *UNIDATA-PATH* to list of static symbols. o Reorder the static symbols in a more logical arrangment so that the spare symbols are at the end. i18n/local/cmucl.pot: o Update
-
rtoy authored
(Even though I (rtoy) should know better, I still find myself writing :cmucl instead of :cmu in feature tests.)
-
rtoy authored
Comment from Paul Foley: Problem: FD-OPEN calls NEXT-VERSION with the namestring; NEXT-VERSION calls EXTRACT-NAME-TYPE-AND-VERSION, which builds a "pattern" when it sees globbing characters in the name, and NEXT-VERSION promptly crashes when it tries to concatenate strings. Fix: Bind *IGNORE-WILDCARDS* to T in NEXT-VERSION (in fd-stream.lisp)
-
- Apr 02, 2011
-
-
rtoy authored
-
- Mar 03, 2011
-
-
rtoy authored
The issue is caused by FAST-READ-CHAR-STRING-REFILL. In some situations the number of octets converted is not exactly the same as the length of the buffer because the last octets in the buffer don't hold a complete encoded character. This is ok, but we didn't update the ibuf-head pointer to indicate that some octets haven't actually been converted. This confuses FILE-POSITION.
-
- Mar 01, 2011
-
-
rtoy authored
Don't need this anymore since the issue appears to be fixed.
-
- Feb 28, 2011
-
-
rtoy authored
SQRT.
-
- Feb 23, 2011
-
-
rtoy authored
#\latin_small_letter_a. This failure is caused by the new SEARCH-DICTIONARY function that does partial completion, and UNICODE-NAME-TO-CODEPOINT function wan't aware of the new way. We could change UNICODE-NAME-TO-CODEPOINT to do the appropriate thing with the new way, but I (rtoy) decided it would be nice to have the old function around too. Hence, restore the old version and use it.
-
- Feb 22, 2011
-
-
rtoy authored
catching setf functions previously.
-
- Feb 17, 2011
-
-
rtoy authored
(OPEN PN :DIRECTION :IO :IF-DOES-NOT-EXIST NIL) no longer signals an error. code/fd-stream.lisp: o Don't try to create a new version if there's no existing file general-info/release-20c.txt: o Update.
-
- Feb 02, 2011
-
-
rtoy authored
not the random symbol DESCRIBE-EXTERNAL-FORMATS.
-
- Feb 01, 2011
-
-
rtoy authored
to trace a local function was checking for the wrong thing.
-
- Jan 27, 2011
-
-
rtoy authored
attribute-table-limit and if the newvalue is #'read-token, we don't actually add the entry to the character-macro-hash-table, because that is the default value for the hash-table. This helps to keep the hash-table size small.
-
- Jan 21, 2011
-
-
rtoy authored
we produce 32-bit binaries instead of the default 64-bit (on 10.6 and later).
-
- Jan 07, 2011
-
-
rtoy authored
freebsd and solaris/x86.
-
- Dec 27, 2010
-
-
rtoy authored
FIND-FOREIGN-FUNCTION-NAME.
-
- Dec 26, 2010
- Dec 22, 2010
- Dec 19, 2010
-
-
rtoy authored
NIL. (From Paul Foley.)
-
- Dec 13, 2010
-
-
rtoy authored
LOAD-DOMAIN return an appropriate entry instead of returning NIL. This still gets rid of all the stats. Solution from Paul Foley.
-
- Dec 11, 2010
-
-
rtoy authored
caused by all the calls to stat in PROBE-FILE in LOCATE-DOMAIN-FILE for files that did not exist. The default locale was C, so every message lookup was causing many stat's to non-exist files. (There were over 1000 calls/sec on a 750 MHz sparc!) So we cache all the calls to PROBE-FILE in LOCATE-DOMAIN-FILE. But just in case, we also allow the user to get at the hash table to examine it (GET-DOMAIN-FILE-CACHE) and also allow the user to clear it (CLEAR-DOMAIN-FILE-CACHE) in case new translations are added without restarting lisp.
-
- Dec 09, 2010
-
-
rtoy authored
-
rtoy authored
the start. This was due to one of two things: The result sequence was created with a negative length, creating invalid objects, or accessing the invalid object would cause a segfault. code/seq.lisp: o Declare the type of LENGTH in MAKE-SEQUENCE-OF-TYPE better. It's not a fixnum, but an index (non-negative fixnum). This should catch any mistakes where we try to create sequences of negative length. o Explicitly catch invalid START and END indices in VECTOR-SUBSEQ* and LIST-SUBSEQ* and signal an error general-info/release-20c.txt: o Document bugfix.
-
- Dec 05, 2010
-
-
rtoy authored
o Fix typo in callback examples. o Add package qualifiers so the examples can be used in CL-USER.
-
- Nov 30, 2010
-
-
rtoy authored
Foley.) o While we're here, canonicalize *FILENAME-ENCODING* using the actual external format name.
-
- Nov 16, 2010
-
-
rtoy authored
Didier Verna, cmucl-imp, 2010-11-11.
-
- Nov 12, 2010
-
-
rtoy authored
a 64-bit boundary. Add st-pad3 to make sure st-blocks is on a 64-bit boundary. Only a problem when cross-compiling from a different arch. The native compile correctly padded the fields.
-