0.9.16.42:

        Always update TN-CURRENT-CONFLICT after the innermost loop of
        PROPAGATE-LIVE-TNS has found a match, and not just every time
        it converts a :READ conflict to a :LIVE conflict. This avoids
        useless travelsals over the tnwise global-conflicts chain, speeding
        up compilation when there are lots of global conflicts (for
        example on (DEBUG 3)). Thanks to David Lichteblau.

diff --git a/src/compiler/life.lisp b/src/compiler/life.lisp
index 6502bc2..8d81428 100644 (file)
--- a/src/compiler/life.lisp
+++ b/src/compiler/life.lisp
@@ -514,10 +514,10 @@
                   (setf (svref (ir2-block-local-tns block1)
                                (global-conflicts-number current))
                         nil)
-                  (setf (global-conflicts-number current) nil)
-                  (setf (tn-current-conflict tn) current))
+                  (setf (global-conflicts-number current) nil))
                  (t
                   (setf (sbit live-in (global-conflicts-number current)) 1)))
+               (setf (tn-current-conflict tn) current)
                (return)))))
         (:write)))
     did-something))

diff --git a/version.lisp-expr b/version.lisp-expr
index c0f797a..2ac1030 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -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".)
-"0.9.16.41"
+"0.9.16.42"