SBCL

cleanup: ROUND-NUMERIC-BOUND issue

Bug #308955 reported by Nikodemus Siivola
4
Affects Status Importance Assigned to Milestone
SBCL
Confirmed
Low
Unassigned

Bug Description

  ROUND-NUMERIC-BOUND assumes that float types always have a FORMAT
  specifying whether they're SINGLE or DOUBLE. This is true for types
  computed by the type system itself, but the compiler type derivation
  short-circuits this and constructs non-canonical types. A temporary
  fix was made to ROUND-NUMERIC-BOUND for the sbcl-0.9.6 release, but
  the right fix is to remove the abstraction violation in the
  compiler's type deriver.

Nikodemus Siivola (nikodemus)
Changed in sbcl:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

Reprioritize as LOW: not user-observable.

Changed in sbcl:
importance: Medium → Low
Revision history for this message
Burton Samograd (burton-samograd) wrote :

So would the fix be in round-numeric-bound or in the type deriver? If in the type deriver, could you point me in the direction of that so I can take a look?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.