- Jan 27, 2006
-
-
rtoy authored
encapsulation. We can't do that because there's nothing to wrap.
-
- Jan 23, 2006
-
-
rtoy authored
with-fixed-allocation and number-dispatch.
-
rtoy authored
work and could probably be implemented better. With these changes (trace (labels foo bar)) will trace the labels function FOO in the function BAR. We only support encapsulate nil, here. No check is made for this. code/ntrace.lisp: o In TRACE-FDEFINITION, recognize a list as a valid function, and return the list as the value of TRACE-FDEFINITION. This seems wrong, but I'm not sure if there's a real fdefinition for it, or if we could create a fake one. code/debug-int.lisp: o In FUNCTION-DEBUG-FUNCTION, recognize a list as the name of a function, and find the corresponding compiled-debug-function and create and return the new compiled-debug-function.
-
rtoy authored
second element isn't a list (and thus doesn't really look like a flet/labels form).
-
- Jan 19, 2006
-
-
rtoy authored
for FreeBSD and NetBSD.
-
- Jan 18, 2006
-
-
rtoy authored
-
- Jan 17, 2006
- Jan 09, 2006
-
-
rtoy authored
the pretty-printer more robust. Bug and fix from Gareth McCaughan, cmucl-imp, 2006-01-09.
-
- Jan 05, 2006
-
-
rtoy authored
MULTIPLE-VALUE-BIND and than like WITH-OPEN-FILE and friends.
-
- Jan 04, 2006
-
-
rtoy authored
were not parsed correctly because the "T" in Tue was being treated as a date-time-divider. Don't allow a date-time-divider to be at the start of the string.
-
- Jan 03, 2006
-
-
rtoy authored
reference information for other conditions. This condition prints out a short message saying to look somewhere appropriate. o Use REFERENCE-CONDITION for the CONSTANT-MODIFIED condition. (Based on SBCL's REFERENCE-CONDITION.) This needs work to add more references.
-
rtoy authored
code/unix.lisp: o Add UNIX-SYSINFO and appropriate constants. code/exports.lisp: o Export UNIX-SYSINFO and corresponding constants. code/sparc-svr4-vm.lisp: o Use UNIX-SYSINFO to provide better values for MACHINE-TYPE and MACHINE-VERSION. Instead of the generic "Ultrasparc", we can return things like "sun4u" and "SUNW,Sun-Blade-1500". Use bootfiles/19c/boot-2005-12-2.lisp to bootstrap this change. Only needed for sparc.
-
- Dec 29, 2005
-
-
rswindells authored
-
- Dec 17, 2005
-
-
rtoy authored
ppc too.
-
- Dec 06, 2005
-
-
rtoy authored
checking to see of the 'STANDARD-OBJECT class exists or not before checking to see if the object is a STANDARD-OBJECT type.
-
- Dec 04, 2005
-
-
rtoy authored
namestring. Bug noted by Lynn Quam, cmucl-imp, 2005/12/02.
-
- Nov 18, 2005
-
-
rtoy authored
of times, regardless of what the body might do to the index variable.
-
- Nov 14, 2005
-
-
rtoy authored
-
- Nov 13, 2005
-
-
rtoy authored
These are the obvious 64-bit integer types. From Luis Oliveira.
-
- Nov 11, 2005
-
-
rtoy authored
first slot gets the natural alignment, but all subsequent slots get 4-byte alignment, even if the object is a double or long long. o Add EMBEDDED-ALIGNMENT to compute this alignment of embedded objects. o Modify PARSE-ALIEN-RECORD-FIELDS to cause the appropriate alignment of slots in a struct.
-
rtoy authored
cmucl-imp, 2005-11-10, with fix. o Apply Walter's fix, because it was missing the fifth arg to GENERALIZED-PEEKING-MECHANISM. o Change GENERALIZED-PEEKING-MACHINISM to use keyword args instead of optional args, to prevent this kind of bug.
-
- Nov 09, 2005
-
-
rtoy authored
-
- Nov 08, 2005
-
-
rtoy authored
#P(<make-pathname args). So most pathnames can be printed readably, even if they have weird components. But we don't handle search-lists and patterns very well because we don't have readable syntax for those. code/sharpm.lisp: o Make the #P reader accept lists and apply make-pathname on them to create the pathname code/pathname.lisp: o If a pathname has no namestring, then try to print out the pathname object using #P(foo) syntax, if possible. If not possible, just print out the pathname unreadably, as we used to. o Put some conditional newlines when printing out unprintable pathnames so it wraps a bit better. (Needs work.)
-
- Nov 07, 2005
-
-
rtoy authored
If the parameter d is omitted, ... except that if the fraction to be printed is zero then a single zero digit should appear after the decimal point. Make it so.
-
rtoy authored
-
rtoy authored
given. We now compute the length more carefully, only checking if to see that the list has the desired minumum and maximum (if applicable) length. This bug was found with ironclad 0.10. (Remove DOTTED-LIST-LENGTH later. We need it now to make bootstrapping easier. I'm lazy.)
-
rtoy authored
-
- Nov 04, 2005
-
-
rtoy authored
component contains a "/" or "." because we can't print these readably.
-
- Oct 24, 2005
-
-
rtoy authored
LOGICAL-PATHNAME-NAMESTRING-P wasn't defined anywhere. o Add LOGICAL-PATHNAME-NAMESTRING-P and adjust LOGICAL-PATHNAME to use it. o Print out identity when printing logical-hosts. (This unrelated change makes it easier to see that the user's BOGUS logical host isn't the same as the BOGUS logical host used in *LOGICAL-PATHNAME-DEFAULTS*.
-
- Oct 22, 2005
-
-
rtoy authored
name. (But we still have problems with print/read for :newest and :unspecific.)
-
- Oct 21, 2005
-
-
rtoy authored
so signal an error when we try to generate the the namestring.
-
rtoy authored
condition, or defstruct, and vice versa, so signal an error if we try to do that.
-
rtoy authored
normally.
-
rtoy authored
converted to an internal number, an error of type reader-error is signaled." So, disable underflow traps, convert the number. If the resulting float is zero, but the number was not, signal a reader-error.
-
rtoy authored
underflow traps are enabled and rehash-threshold is very small.
-
- Oct 20, 2005
-
-
rtoy authored
10), and (log 17 10) returned different single-float results. I think this is allowed by ANSI CL, but I think it's unfortunate. Therefore, try to apply float contagion to the arguments before computing the log function. Also, if both args are single-floats or rationals, we coerce them to double-floats before computing the result. This makes (log 17 10) = (log 17.0 10). There are other cases still to be considered.
-
- Oct 19, 2005
-
-
rtoy authored
nreverse) modify constant args and for warning when the result of destructive functions is not used. Detecting modification of constant args is done by adding a new IR1 transformation that checks that a function is not destructively modifying constants or literals. A new IR1 attribute, important-result, is used to determine if the result of a function should be used instead of discarded. (Note: this means some functions are not detected. This should probably be implemented as another transform so the compiler can detect those cases.) code/error.lisp: o Add new condition CONSTANT-MODIFIED. compiler/fndb.lisp: o Note destructive functions that should not modify constant args o Note destructive functions whose results should be used. compiler/ir1opt.lisp: o Add new function CHECK-IMPORTANT-RESULT to check if the result is used. o Update IR1-OPTIMIZE-COMBINATION to check if a function destructively modifies constant args or if the result of a destructive function is not used. compiler/knownfun.lisp: o Add new IR1 attribute, IMPORTANT-RESULT, to indicate that the result of a function should be used. o Add new FUNCTION-INFO slot, DESTROYED-CONSTANT-ARGS. This holds a function for computing the constant or literal arguments which are destructively modified by the function. o Add support functions for DESTROYED-CONSTANT-ARGS functions.
-
- Oct 18, 2005
-
-
rtoy authored
failures, so let's preserve the status quo until we can fix these all of these issues.
-
- Oct 14, 2005
-
-
rtoy authored
restarts. Bug reported by Helmut Eller, cmucl-imp, 2005-02-27. Solution by Nikodemus Siivola, cmucl-imp, 2005-10-12.
-