- Dec 08, 2022
-
-
Raymond Toy authored
-
- Nov 25, 2022
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Nov 02, 2022
-
-
Raymond Toy authored
-
- Oct 31, 2022
-
-
Raymond Toy authored
-
- Oct 17, 2022
-
-
Raymond Toy authored
-
- Oct 15, 2022
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Aug 08, 2022
-
-
Raymond Toy authored
-
- Dec 16, 2021
-
-
Raymond Toy authored
-
- Feb 04, 2021
-
-
Raymond Toy authored
We shouldn't get an overflow, but we do because clang 10 miscompiles e_pow.c and causes an overflow. Addresses #101
-
- Sep 22, 2018
-
-
Raymond Toy authored
-
- Jul 21, 2018
-
-
Raymond Toy authored
-
- Jul 15, 2018
-
-
Raymond Toy authored
-
- 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 04, 2018
-
-
Raymond Toy authored
-
- Feb 03, 2018
-
-
Raymond Toy authored
-
- Jan 29, 2018
-
-
Raymond Toy authored
* Print multiple splices correclty without the extra set of parenthesis around each splice. * Add test for this.
-
- Sep 30, 2017
-
-
Raymond Toy authored
Add the tests given in issue #45.
-
- Sep 09, 2017
-
-
Raymond Toy authored
The main problem is that we weren't calling wait3 with WCONTINUED so that we would be signaled when the process continues. And we also need to check that result of wait call was WCONTINUED> Replace the wait3 routine with a C routine (prog_status) so we don't have to deal with the OS-specific flags. This function basically returns what the lisp function wait3 did. Use this function in GET-PROCESSES-STATUS-CHANGES. - runprog.c: - Add prog_status - run-program.lisp: - Use prog_status instead of wait3 - issues.lisp: - Add basic test
-
- Dec 02, 2016
-
-
Raymond Toy authored
Don't use cl:assert for the lisp-unit test; it should use lisp-unit assertions.
-
- Nov 30, 2016
-
-
Raymond Toy authored
-
- Nov 29, 2016
-
-
Raymond Toy authored
Basically used the repro case from the issue.
-
- Nov 11, 2016
-
-
Raymond Toy authored
Allow 1899 as a year, but also add a check that the resulting time is a non-negative integer. Add a test for this too in issues.lisp.
-
- Oct 03, 2016
-
-
Elias Pipping authored
-
- Sep 26, 2016
-
-
Raymond Toy authored
-
- Sep 10, 2016
-
-
Raymond Toy authored
-
- Sep 08, 2016
-
-
Raymond Toy authored
-
Raymond Toy authored
-
- Aug 21, 2016
-
-
Raymond Toy authored
When writing a string to the program too few octets were written because strings are now 16-bits wide. To fix this, only write the low 8-bits of each character. This matches what reading does. This pretty much implies that the caller should use STREAM:STRING-ENCODE and STREAM::STRING-DECODE on the strings. Add several tests to verify the expected results.
-
- May 14, 2016
-
-
Raymond Toy authored
src/compiler/float.lisp: o The deftransform coerce was checking for a type of 'float and using %single-float to do the conversion. This is incorrect; it should only apply if the type is 'single-float. tests/issues.lisp o Add test for this. Verified that the test fails on the current snapshot and ix fixed by this change.
-
- Oct 17, 2015
-
-
Raymond Toy authored
Covers 1, 2, and 4-bit arrays. Manually verified that the cmucl 21a fails these tests, as expected, when the index is a multiple of the number of elements per 32-bit word.
-
- Aug 01, 2015
-
-
Raymond Toy authored
o Add declaration for LIST-ELT* that the index is a kerrnel:index. o Clean up ELT to directly call LIST-ELT* instead of having an inlined version. o Fix typo: issue.5 is really issue.4. o Add tests for invalid indices for ELT and (SETF ELT) for both lists and vectors.
-
- Jun 24, 2015
-
-
Raymond Toy authored
Fix #7 The change to use extended names like (flet frob) broke the detection of local names for get-setf-expansion. Fix it. This reverts behavior back to what 18a used to do. A test for this is also added.
-
- Jun 22, 2015
-
-
Raymond Toy authored
Fix #3. The lookup for the names was not handling things like (FLET SQUARE TEST/PRESENT) correctly. Use VALID-FUNCTION-NAME to get the function name instead of a plain EQUAL test.
-
- Jun 14, 2015
-
-
Raymond Toy authored
code/seq.lisp: o Define internal LIST-ELT* function that executes ELT on lists, signaling an error if the index is invalid. compiler/seqtran.lisp: o Change the deftransform for ELT to use LIST-ELT* instead of NTH. tests/issues.lisp: o Add test for this issue.
-
- Apr 25, 2015
-
-
Raymond Toy authored
Also added tests/issues.lisp with a corresponding test.
-