- Feb 18, 2020
-
-
Raymond Toy authored
When `REQUIRE` is called, autoload ASDF if it hasn't already been loaded. User's no longer have to load asdf explicitly anymore. Update release notes.
-
- Feb 16, 2020
-
-
Raymond Toy authored
-
- May 29, 2019
-
-
Raymond Toy authored
[skip ci]
-
Raymond Toy authored
This reverts commit 4dbd847a. release-21d.md was erroneously modified. It should have been done to release-21e.md, a new file. We've already released 21d.
-
Raymond Toy authored
This reverts commit 1ca3f155.
-
- May 28, 2019
-
-
Raymond Toy authored
[skip ci]
-
Raymond Toy authored
* Update to ASDF 3.3.3 * Note that gcc -O1 can build cmucl now for gcc 8.1.1 and later. * Added x86_linux_clang to build cmucl with clang on linux
-
- Apr 17, 2019
-
-
Raymond Toy authored
-
Raymond Toy authored
As reported gcc 8.1.1 can't produce a working lisp. gcc 8.3.1 also fails. But as reported on cmucl-imp, 2019-04-08, by Juan Pablo Hierro Alverez, -O1 works. Use -O1.
-
- Dec 17, 2018
-
-
Raymond Toy authored
-
- Dec 08, 2018
-
-
Raymond Toy authored
-
- Dec 06, 2018
-
-
Raymond Toy authored
-
- Oct 12, 2018
-
-
Raymond Toy authored
- Oct 07, 2018
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Sep 22, 2018
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Aug 25, 2018
-
-
Raymond Toy authored
Add `Config.x86_linux_clang` to use clang instead of gcc to build cmucl. update `create-target.sh` so that it sets the motif variant correctly when using `Config.x86_linux_clang` See issue #68. With this config, Fedora 28 successfully builds cmucl and passes all the tests.
-
- Aug 05, 2018
-
-
Raymond Toy authored
clang complains: warning: incompatible pointer to integer conversion passing 'lispobj *' (aka 'unsigned long *') to parameter of type 'lispobj' (aka 'unsigned long'); dereference with * [-Wint-conversion] || in_range_p(addr, control_stack, control_stack_size) So cast control_stack to lispobj. Same complaint for binding_stack too.
-
Raymond Toy authored
-
Raymond Toy authored
The compiler complained that these symbols were also being exported from the XLIB package. Just add them to the defpackage to silence the warnings.
-
- Jul 27, 2018
-
-
Raymond Toy authored
-
- Jul 22, 2018
-
-
Raymond Toy authored
The TRAPS and EXCEPTION vars in the WITH-FLOAT-TRAPS were unused. Remove them. Also add some tests for WITH-FLOAT-TRAPS-MASKED to verify that the traps are masked.
-
Raymond Toy authored
Replace :random-mt19937 with :random-xoroshiro in the cross-compile scripts.
-
- Jul 15, 2018
-
-
Raymond Toy authored
The code for applying the correction is pretty much identical for each negative operant, so add a routine to do that.
-
- Jul 04, 2018
-
-
Raymond Toy authored
Update tests to reflect the change in names.
-
Raymond Toy authored
The current bignum multiplier creates temp space to hold the absolute value of the bignums and then negates the result (in-place) at the end. Instead, use the algorithm from Hacker's Delight that pretends the numbers are unsigned, does the unsigned multiply and finally corrects the result. No extra memory is needed for this.
-
- May 12, 2018
-
-
Raymond Toy authored
-
- Mar 14, 2018
-
-
Raymond Toy authored
Just change the date on the manual to the date of the 21c release. Now that we can create the html pages again with hevea, we can update this.
-
- Mar 05, 2018
-
-
Philip Fominykh authored
-
Philip Fominykh authored
Added argument #5 to \layout to act as prelude. Putting index and spacing commands there eliminates extra paragraph.
-
- Feb 19, 2018
-
-
Raymond Toy authored
Fixes #61 and #62. The `ARRAY-HAS-FILL-POINTER-P` and `ARRAY-DISPLACEMENT` functions are declared inline and the compiler tries to constant-fold these inlined functions operating on simple arrays. Thus don't allow the compiler to constant-fold calls to `%ARRAY-FILL-POINTER-P`. This is normally protected by a call to `ARRAY-HEADER-P`, but when it's inlined, the compiler tries to constant-fold `%ARRAY-FILL-POINTER-P` on an array without such a slot. Likewise `ARRAY-DISPLACEMENT` calls `%ARRAY-DISPLACED-P`, `%ARRAY-DATA-VECTOR`, and `%ARRAY-DISPLACEMENT`, and the calls are protected by `ARRAY-HEADER-P`. So don't constant-fold these either. Maybe we could also make CONSTANT-FOLD-CALL be smarter about this? * src/compiler/generic/objdef.lisp * Remove flushable from these ref-trans methods. * src/general-info/release-21d.md * Update * tests/issues.lisp * Add tests from the bug reports.
-
- Feb 18, 2018
-
-
Raymond Toy authored
The deftransforms `upgraded-complex-real-contagion-arg1` and `upgraded-complex-real-contagion-arg2` were coercing the complex number to the exact type of the float number. Because of the `THE` form, the type of the float was `(member 1d0)`, so the compiler was coercing `#c(1/2 1/2)` to `(complex (double-float 1d0))`, which is wrong. Therefore, coerce the complex to just the type format of the real part, ignoring any bounds. * src/compiler/float-tran.lisp * Coerce to format type, discarding any bounds * src/general-info/release-21d.md * Update notes * tests/issues.lisp * Added test for this
-
Raymond Toy authored
Remove the symbol `C::%UNARY-FROUND` and just let the compiler package inherit it from the kernel package. * src/bootfiles/21c/boot-2018-02-1.lisp * Use this to bootstrap the change (by uninterning the symbol) * src/code/float.lisp * Just export %unary-fround * src/general-info/release-21d.md * Update * tests/issues.lisp * Add test for this issue
-
- Feb 13, 2018
-
-
Philip Fominykh authored
-
Philip Fominykh authored
-
- Feb 10, 2018
-
- Feb 04, 2018
-
-
Raymond Toy authored
If 0 is the lower bound then the smallest exponent is not for 0, but for the least positive float because of denormals. Also handle exclusive bounds.
-
- Feb 03, 2018
-
-
Raymond Toy authored
Type derivation for exponent part of decode-float was incorrect. We need to take the absolute value of the argument before deriving the type since the exponent is, of course, independent of the sign of the number. In the test case, the negative interval caused the lower and upper bounds to be reversed, resulting in an invalid interval.
-