From 70b1ac2e57701862aa96a0b82ad3c317b88b36a7 Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Fri, 9 Nov 2018 15:41:55 -0500 Subject: [PATCH] Revert experimental changes These crash the earley benchmark --- scheme/cyclone/cps-optimizations.sld | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/scheme/cyclone/cps-optimizations.sld b/scheme/cyclone/cps-optimizations.sld index a89571f2..9fa75a88 100644 --- a/scheme/cyclone/cps-optimizations.sld +++ b/scheme/cyclone/cps-optimizations.sld @@ -589,7 +589,7 @@ (cond ((and (prim:mutates? (car exp)) ;; loop3-dev WIP step #1 - do not immediately reject these prims - (not (member (car exp) '(vector-set!))) ;; TODO: experimental + ;(not (member (car exp) '(vector-set!))) ;; TODO: experimental ) (let ((e (cadr exp))) (when (ref? e) @@ -1297,14 +1297,14 @@ (inline-ok? e ivars args arg-used return))) (reverse (cdr exp)))) ;; loop3-dev WIP step #2 - some args can be safely ignored - ((and (prim? (car exp)) - (prim:mutates? (car exp)) - (member (car exp) '(vector-set!)) - ) - ;; with vector-set, only arg 1 (the vector) is actually mutated - ;; TODO: is this always true? do we have problems with self-recursive vecs?? - (inline-ok? (cadr exp) ivars args arg-used return) - ) + ;((and (prim? (car exp)) + ; (prim:mutates? (car exp)) + ; (member (car exp) '(vector-set!)) + ; ) + ; ;; with vector-set, only arg 1 (the vector) is actually mutated + ; ;; TODO: is this always true? do we have problems with self-recursive vecs?? + ; (inline-ok? (cadr exp) ivars args arg-used return) + ;) (else (for-each (lambda (e)