- Sep 28, 2004
-
-
rtoy authored
ensure-profile-fwrapper was not able to create profile fwrappers for 4 or more args. This is a hack; I don't know why the original version doesn't work.
-
- Sep 27, 2004
-
-
rtoy authored
determine if an array can be printed readably.
-
rtoy authored
(0 1 2 0 1 2) instead of (0 1 2 0 1 2 0 1 2). Bug fix from Peter Graves, via cmucl-imp, 2004-09-27.
-
rtoy authored
needs to be rethought because there's confusion on what pathnames can be printed readably or not. In particular (probe-file "logical-host:dir;") gets an error because there's a merge-pathname that creates a pathname without a name, but version :newest.
-
- Sep 25, 2004
-
-
rtoy authored
specializer. Fixes a bug reported by Bruno Haible, cmucl-imp, 2004-09-15.
-
- Sep 24, 2004
- Sep 23, 2004
-
-
rtoy authored
it always DPB'ed the result into -1, which always results in a negative number. We need to check the most significant bit to decide what to do.
-
rtoy authored
if the range of the arg were too large to fit in a float. Silently return unbounded value instead of signaling an error during compilation.
-
- Sep 21, 2004
- Sep 14, 2004
-
-
rtoy authored
because it calls handle_breakpoint which eventually calls into Lisp. Gencgc allocation needs SIGILL enabled.
-
- Sep 13, 2004
- Sep 11, 2004
-
-
rtoy authored
double-float-epsilon actually be epsilon on x86. No effect on other ports. The default precision is now 53-bit (double-float) instead of 64-bit (80-bit floats). However, to preserve C expectations, all calls to C have the precision set to 64-bit. This slows down calls to C, but we try to make syscalls and such fast by not changing precision for the call. By default ext:float-accuracy is 3. Use boot7.lisp to bootstrap.
-
- Sep 10, 2004
-
-
rtoy authored
the array element-type is T.
-
- Sep 09, 2004
-
-
rtoy authored
readably, instead of a generic error condition.
-
rtoy authored
the next argument in the list: (format nil "~:{ ~A, ~^ and ~A, ~}" '((foo) (bar baz))) => " FOO, " instead of " FOO, BAR, and BAZ, " From a bug noted by Sean Champ on #lisp.
-
rtoy authored
(Bug from Bruno Haible, cmucl-imp 2004-09-08.)
-
- Sep 08, 2004
-
-
rtoy authored
(Should we have it do something else for (EQL 0)?)
-
rtoy authored
the compiler about what COMPLEX and (COMPLEX REAL) are. They should be the same. - Make (COMPLEX *) be the same as (COMPLEX REAL), because we were creating a plain COMPLEX, which isn't what we want. - If the typespec is a subtype of RATIONAL, return (COMPLEX RATIONAL). o Make (COMPLEX REAL) print out as COMPLEX instead of as a union of specialized complex types. o Modify CTYPE-OF-NUMBER so that it no longer creates (COMPLEX (INTEGER low high)) types; these are now (COMPLEX RATIONAL). This fixes a bug where (type-of #c(0 1/2)) was giving an error. (This is fixes the bug by removing the offending code. But do we really want and need to support (COMPLEX INTEGER) types in the compiler? Shouldn't (COMPLEX RATIONAL) be good enough?)
-
rtoy authored
boot6-sxhash to bootstrap this change for ppc.
-
- Sep 07, 2004
-
-
rtoy authored
#.(logical-pathname "...").
-
- Sep 03, 2004
-
-
rtoy authored
be a union type.
-
rtoy authored
If an object to be recursively printed has components and is at a level equal to or greater than the value of *print-level*, then the object is printed as ``#''. Adjust the default structure printer and %print-unreadable-object to do this. This fixes the PRINT-LEVEL.2, PRINT-LEVEL.6, PRINT-LEVEL.8, and PRINT-LEVEL.9. test failures.
-
- Sep 02, 2004
-
-
rtoy authored
silently truncate that to integer. o PPRINT-LOGICAL-BLOCK is supposed to signal a type-error if :suffix, :prefix, or :per-line-prefix is supplied but is not a string. We check for this, and make sure we don't pass in NIL in other parts of the code. These issues were found in ansi-tests.
-
- Sep 01, 2004
- Aug 31, 2004
-
-
rtoy authored
-
rtoy authored
as ~W, ~_, ~<...~:>, ~I, or ~:T. This should signal an error, according to CLHS 22.3.5.2.
-
rtoy authored
o format.r.8: (format nil "~vr" nil 5) is supposed to print "five", not "5". o format.logical-block.23: ~<...~:@> is supposed to add fill-style conditional newlines after each group of blanks in the body, EXCEPT for blanks after a <Newline> directive.
-
rtoy authored
sure the pages are not write-protected, because the kernel doesn't like that. Also update it to touch the beginning of every page. Use this idea in unix-glibc2.lisp. This is a workaround for the bug reported by David Lichteblau on Aug 26, 2004 (for a long-standing bug fomr Dec 7, 1999).
-
rtoy authored
the places where it is used. o Remove old bignum-gcd.
-
- Aug 30, 2004
-
-
rtoy authored
o Previous changes were wrong. This version handles relative and section-relative columns correctly, I think. PPRINT-TABULAR o The computation of colinc was wrong---I don't think we need to add one to tabsize. o I don't think we should output the space character. It results in one extra space. With these changes, the format tests in ansi-tests for ~T and friends pass. I think these are right now, but I'm not 100% sure.
-
rtoy authored
(debug-return). No bootstrap file or cross-compile needed. Return-from-frame only works when debug = 3.
-
- Aug 28, 2004
-
-
rtoy authored
tabbing.
-
rtoy authored
was at or beyond colnum. o COMPUTE-TAB-SIZE was crashing if colinc was zero, instead of returning 0. o PPRINT-TABULAR was passing the specified tabsize to PPRINT-TAB. I think it should be incremented by one to specify the correct colinc for PPRINT-TAB. These fixes correct some of the errors found by ANSI-TESTS.
-
rtoy authored
-
- Aug 27, 2004
-
-
rtoy authored
-