Hello Juan Jose. I have tested the last git version of ECL - e90b2f12, and compared it with one of the recent versions tested not so far ago - ce653d88.
Please check this report: http://common-lisp.net/project/cl-test-grid/ecl-lisp-to-c.html It presents only results which are different on the two compilers (exclusive-or between results for old version and for new one). If the left column (old compiler) has red result and the right column (new compiler) has green result, it is an improvement. If the left is green and the right is red - it is a regression. What deserve attention here are problems of loading cl-json.test and clem ASFD systems. Probably they are caused by the same error. I reproduced them in REPL like this: #rm ~/.cache/common-lisp/ (require :cmp) (ql:quickload :cl-json) (ql:quickload :cl-json.test) => stack overflow ;;;; the second problem (ql:quickload :clem) => stack overvlow (the first time you run this) or "The function CLEM:ARRAY->SB8-MATRIX is undefined." (if you restart ECL and run it again). The bytecode compiler seems to have the same problems (or maybe it's a single problem), plus it has another error In form (#<foreign-built-in-type :UNSIGNED-CHAR>) FUNCTION: Not a valid argument #<foreign-built-in-type :UNSIGNED-CHAR>. Here is the bytecode report: http://common-lisp.net/project/cl-test-grid/ecl-bytecode.html Best regards, - Anton ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Ecls-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecls-list
