Update of /cvsroot/sbcl/sbcl
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv23509
188.8.131.52: better reporting for failure to stack allocate
* If the LVAR has no uses left, it is not good for DX.
* When flushing the destination of a DX lvar, note that its uses will
not be stack allocated.
* Pull out the failure to stack allocate reporting into
NOTE-NO-STACK-ALLOCATION, relax the filter to allow complaints
about non-constant REFs, and omit notes for flushed and flushable
combinations. TODO: the compiler should know about non-consing
functions, so that it can avoid inane notes like "could not stack
allocate the result of (CAR X)" should someone declare that DX.
* Muffle compiler notes from WITH-PINNED-OBJECTS, since our paranoid
use of DX-LET there is liable to cause lots of confusing "unable to
stack allocate" notes.
RCS file: /cvsroot/sbcl/sbcl/NEWS,v
retrieving revision 1.1535
retrieving revision 1.1536
diff -u -d -r1.1535 -r1.1536
--- NEWS 5 Jun 2009 11:36:46 -0000 1.1535
+++ NEWS 5 Jun 2009 13:08:35 -0000 1.1536
@@ -1,6 +1,9 @@
;;;; -*- coding: utf-8; fill-column: 78 -*-
* optimization: more efficient type-checks for FIXNUMs when the value
is known to be a signed word on x86 and x86-64.
+ * improvement: failure to provide requested stack allocation compiler notes
+ provided in all cases (requested stack allocation not happening without a
+ note being issued is now considered a bug.)
* bug fix: on 64 bit platforms FILL worked incorrectly on arrays with
upgraded element type (COMPLEX SINGLE-FLOAT), regression from 184.108.40.206.
(thanks to Paul Khuong)
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.4497
retrieving revision 1.4498
diff -u -d -r1.4497 -r1.4498
--- version.lisp-expr 5 Jun 2009 11:36:47 -0000 1.4497
+++ version.lisp-expr 5 Jun 2009 13:08:35 -0000 1.4498
@@ -17,4 +17,4 @@
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)