FILL behaving oddly in compiled code

Bug #1732553 reported by Paul F. Dietz on 2017-11-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Undecided
Unassigned

Bug Description

(defun f26 (p2)
  (declare (optimize (speed 2) (safety 0) (debug 0) (space 1))
           (type (array t (*)) p2)
           )
  (fill p2 nil))

(f26 (make-array '(3) :initial-element t :fill-pointer 2))
==>
#(NIL NIL T)

(array-has-fill-pointer-p *)
==>
NIL

(fill (make-array '(3) :initial-element t :fill-pointer 2) nil)
==>
#(NIL NIL)

(array-has-fill-pointer-p *)
==>
T

Stas Boukarev (stassats) on 2017-11-16
Changed in sbcl:
assignee: nobody → Stas Boukarev (stassats)
Stas Boukarev (stassats) on 2017-11-16
Changed in sbcl:
assignee: Stas Boukarev (stassats) → nobody
Stas Boukarev (stassats) wrote :

In d6351c3887ff13f7fba1fde6b86a0eb75d972be2

Changed in sbcl:
status: New → Fix Committed
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers