- Sep 20, 2011
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Sep 19, 2011
-
-
Raymond Toy authored
-
- Sep 18, 2011
-
-
Raymond Toy authored
-
- Sep 03, 2011
-
-
rtoy authored
-
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
-
rtoy authored
We don't need sigbus_handler_tramp; sigbus_handle_now is good enough. Print out the PC too when we get a real sigbus.
-
- Sep 01, 2011
-
-
rtoy authored
-
rtoy authored
-
rtoy authored
On Linux, os_init can re-exec lisp to set up the correct personality. Not normally a problem, but if any output happens before os_init is called, the output appears to happen twice. So add os_init0 to do this early on, before any output. This is a bit of a kludge. lisp/lisp.c: o Call os_init0 early in main. lisp/Linux-os.c: o Move the personality stuff from os_init to os_init0. lisp/Darwin-os.c: lisp/FreeBSD-os.c: lisp/NetBSD-os.c: lisp/OpenBSD-os.c: lisp/hpux-os.c: lisp/irix-os.c: lisp/mach-os.c: lisp/osf1-os.c: lisp/solaris-os.c: lisp/sunos-os.c: o Add dummy implementation of os_init0. These OSes don't (currently) need anything special. lisp/os.h: o Declare os_init0.
-
rtoy authored
stack overflows would crash lisp. Darwin-os.c: o Need to check for stack overflow in the sigbus handler. (Without that, it's treated as a regular bus error.) o Add the rest of the infrastructure to handle the stack overflow. release-20c.txt: o Update
-
- Aug 23, 2011
-
-
rtoy authored
general-info/release-20c.txt o Update to asdf2 2.017.
-
- Aug 21, 2011
- Jul 12, 2011
- Jun 29, 2011
-
-
rtoy authored
o Add note about build-all.sh.
-
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 28, 2011
-
-
rtoy authored
-
- Jun 27, 2011
-
-
rtoy authored
o Unicode updated to version 6.0.0. o Trac #43 repoened because that change was reverted.
-
rtoy authored
o Add usage message. o Don't include the emacs-style backup files that are sometimes created for the pot files.
-
rtoy authored
-
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
o Update the version number for ASDF.
-
rtoy authored
There's no reason why this shouldn't work and tests show that it does work. So instead of disallowing it, just print a warning that it is unusual. Fred also said this should work; it's just a bit odd running a 30MB executable with a 30MB core.
-
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
- Jun 06, 2011
-
-
rtoy authored
-
- Jun 05, 2011
-
-
rtoy authored
-
- 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)
-
- May 11, 2011
-
-
rtoy authored
-
- Apr 12, 2011
-
-
rtoy authored
-
- Apr 11, 2011
- Apr 03, 2011