Custom Query (1030 matches)
Results (751 - 753 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1388 | fixed | wrong sign in ratio to single-float coercion | ||
| Description |
[From Gilbert Baumann] I found a bug with coercion of RATIOs to SINGLE-FLOATs, like:
Which has the wrong sign. This only happens with the 64 bit version and not with the 32 bit version. I consider that a pretty serious bug. Here is the patch, it fixes %SHORT-FLOAT-RATIO. *** l0-float.lisp Sat Sep 24 00:12:44 2016
--- l0-float-fixed.lisp Sat Sep 24 00:13:43 2016
***************
*** 528,534 ****
(make-short-float-from-fixnums
(ldb (byte IEEE-single-float-digits (- intlen IEEE-single-float-digits)) int)
new-exp
! (if minusp 1 0)))
; den > num - exp negative
(progn
(float-rat-neg-exp num den (if minusp -1 1) nil t)))))))))
--- 528,534 ----
(make-short-float-from-fixnums
(ldb (byte IEEE-single-float-digits (- intlen IEEE-single-float-digits)) int)
new-exp
! (if minusp -1 1)))
; den > num - exp negative
(progn
(float-rat-neg-exp num den (if minusp -1 1) nil t)))))))))
|
|||
| #1390 | fixed | *print-string-length* control for tracing, backtracing, and errors | ||
| Description |
It would be nice to be able to control the length of string printouts in tracing, backtracing, and error situations. This is analogous to the control over *print-length* and *print-level* that are already provided by CCL. When debugging code that deals with very long strings, this is essential. IOW, add *trace-print-string-length* analogous to *trace-print-length* and *trace-print-level* for use in tracing; add *backtrace-print-string-length* analogous to *backtrace-print-length* and *backtrace-print-level* for use in backtracing; and add *error-print-string-length* analogous to *error-print-length* and *error-print-level* for use in error messages. |
|||
| #1391 | fixed | Building on FreeBSD 11.x and later broken due to MAP_NORESERVE | ||
| Description |
|
|||
