Compiler goes into loop on FIND-IF-NOT with certain declarations
Bug #1790157 reported by
Paul F. Dietz
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SBCL |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
(lambda (p1 p3 p4)
(declare (optimize (speed 0) (debug 2))
(type (or (eql #.#'oddp) (satisfies eval)) p1))
(find-if-not p1 nil p3 p4))
==>
compiler does not return, eventually runs out of memory
| Changed in sbcl: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Stas Boukarev (stassats) |
Revision history for this message
| Paul F. Dietz (paul-f-dietz) wrote | #1 |
Revision history for this message
| Stas Boukarev (stassats) wrote | #2 |
| Changed in sbcl: | |
| assignee: | Stas Boukarev (stassats) → nobody |
| status: | New → Fix Committed |
| Changed in sbcl: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Another similar example:
(lambda (p1 p2 p3)
(declare (optimize (speed 0) (debug 2))
(type (or (satisfies #:foo) (eql #:x)) p1))
(count-if p1 p2 p3 #'identity))