armedbear-ticket January 2012

armedbear-ticket@common-lisp.net

1 participants
37 discussions

[armedbear-ticket] [armedbear] #168: Compilation fails for quicklisp let-plus
by armedbear 08 Aug '12

08 Aug '12

#168: Compilation fails for quicklisp let-plus ----------------------------------------+----------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 0.28 Component: compiler | Version: Keywords: quicklisp ansi_confromance | ----------------------------------------+----------------------------------- let-plus-20110730-git, a dependency for LLA, cannot be compiled resulting in the following error: {{{ ; Loading /Users/evenson/.cache/common-lisp/abcl-0.27.0-dev-fasl37-macosx- java/Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/package.abcl ... ; Loaded /Users/evenson/.cache/common-lisp/abcl-0.27.0-dev-fasl37-macosx- java/Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/package.abcl (0.027 seconds) ; Compiling /Users/evenson/quicklisp/dists/quicklisp/software/let- plus-20110730-git/let-plus.lisp ... ; (IN-PACKAGE #:LET-PLUS) ; (DEFUN IGNORED? ...) ; (DEFUN REPLACE-IGNORED ...) ; (DEFUN EXPAND-SLOT-FORMS ...) ; (DEFUN EXPAND-ENTRY-FORMS ...) ; (DEFUN EXPAND-ARRAY-ELEMENTS ...) ; (DEFGENERIC LET+-EXPANSION ...) ; (DEFGENERIC LET+-EXPANSION-FOR-LIST ...) ; (DEFMACRO LET+ ...) ; (DEFMACRO DEFINE-LET+-EXPANSION ...) #<THREAD "interpreter" {52BBC66F}>: Debugger invoked on condition of type COMPILER-UNSUPPORTED-FEATURE-ERROR COMPILE-FORM unhandled case ((ANAPHORA:IT #:THIS-S2842)) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/168> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 6

[armedbear-ticket] [armedbear] #73: "normalize-type" buffering
by armedbear 08 Aug '12

08 Aug '12

#73: "normalize-type" buffering -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: task | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: performance | -------------------------+-------------------------------------------------- Peter Graves points out that with his "canonicalize-type" buffering, he achieved measurable performance gain in XCL. We want to do the same in ABCL. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/73> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #175: abcl.release target fails occasionally
by armedbear 29 Jul '12

29 Jul '12

#175: abcl.release target fails occasionally --------------------------+------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 1.0 Component: build | Version: 0.27 Keywords: abcl.release | --------------------------+------------------------------------------------- The central abcl.release target can fail unpredictably, so it is current best to clean the intermediate build targets before making a release. 'abcl.release' currently *always* fails under MSFT Windows. @erik had noted this in #abcl. http://trac.common-lisp.net/armedbear/changeset/12419 -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/175> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #60: Implement USE-FAST-CALLS properly
by armedbear 29 Jul '12

29 Jul '12

#60: Implement USE-FAST-CALLS properly -------------------------+-------------------------------------------------- Reporter: trittweiler | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- USE-FAST-CALLS is implemented at the moment by flipping an essentially global variable. The proper implementation would be to make turn it into a ABCL-specific declaration, and making sure it affects its lexically enclosing code only. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/60> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #191: Compiling SHARPSIGN SHARPSIGN form causes stack overflow
by armedbear 28 Jul '12

28 Jul '12

#191: Compiling SHARPSIGN SHARPSIGN form causes stack overflow ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: major | Milestone: 1.0.1 Component: compiler | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2142 Anton reports] that compiling the alexandria tests from Quicklisp 2011-12-03 results in a stack overflow. The offending form seems to be {{{ (deftest circular-tree-p.2 (alexandria:circular-tree-p '#1=(#1#)) t) }}} where the problem seems to occur in the compiling ADD-ENTRY function {{{ 0: (#<FUNCTION {47D2FBB5}> #<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>) 1: (APPLY #<FUNCTION {47D2FBB5}> (#<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>)) 2: (SYSTEM::RUN-HOOK SYSTEM::*INVOKE-DEBUGGER-HOOK* #<STORAGE-CONDITION {18010D30}> #<FUNCTION {47D2FBB5}>) 3: (INVOKE-DEBUGGER #<STORAGE-CONDITION {18010D30}>) […] 31: org.armedbear.lisp.Primitives$pf_apply.execute(Primitives.java:2853) 32: (#<FUNCTION {5F4298A5}>) 33: (JRUN-EXCEPTION-PROTECTED #<FUNCTION {5F4298A5}>) 34: (SYSTEM::CONVERT-TOPLEVEL-FORM (REGRESSION-TEST::ADD-ENTRY (REGRESSION-TEST::MAKE-ENTRY :PEND T :NAME 'ALEXANDRIA-TESTS::CIRCULAR- TREE-P.2 :PROPS ...)) NIL) 35: (SYSTEM::PROCESS-TOPLEVEL-FORM (REGRESSION-TEST::ADD-ENTRY (REGRESSION-TEST::MAKE-ENTRY :PEND T :NAME 'ALEXANDRIA-TESTS::CIRCULAR- TREE-P.2 :PROPS ...)) #<FILE-STREAM {D33A97F}> NIL) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/191> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #32: Modify the currently disabled runtime-class.lisp code to not require ASM
by armedbear 28 Jul '12

28 Jul '12

#32: Modify the currently disabled runtime-class.lisp code to not require ASM --------------------------------------------------------------------+------- Reporter: vvoutilainen | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: jvm bytecode compiler runtime dynamic class generation | --------------------------------------------------------------------+------- It's possible to define classes at runtime, by generating bytecode and loading it from the generated binary data, without ever writing it to a temporary file. runtime-class.lisp does that, but it requires an external bytecode library (ASM). ABCL has all the functionality for this to be done without ASM, so the task is to modify the runtime-class.lisp code so that ASM is no longer required and the code can be taken to be part of the build. -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/32> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #137: CLtL2 environment support
by armedbear 28 Jul '12

28 Jul '12

#137: CLtL2 environment support -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: minor | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- Cyrus Harmon requests support for [http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node102.html#SECTION001250000… CLtL2 environment] objects support for his pixel access library, as described in a [http://cyrusharmon.org/blog/display?id=113 recent blog post] on [https://github.com/slyrus/opticl/blob/master/opticl.lisp opticl]. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/137> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #55: Clearing LispThread.currentThread()._values more efficiently
by armedbear 28 Jul '12

28 Jul '12

#55: Clearing LispThread.currentThread()._values more efficiently -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- We currently clear _values all over the place; we could be more efficient some times. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/55> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 8

[armedbear-ticket] [armedbear] #192: ASDF::IMPLEMENTATION-IDENTIFIER contains information on which ABCL was compiled
by armedbear 28 Jul '12

28 Jul '12

#192: ASDF::IMPLEMENTATION-IDENTIFIER contains information on which ABCL was compiled ------------------------------+--------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: trivial | Milestone: unscheduled Component: (A)MOP | Version: 1.0 Keywords: asdf, bite-sized | ------------------------------+--------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/2169 Anton Vodonosov reports on armedbear-develop@] that the ASDF IMPLEMETATION-IDENTIFIER contains a reference to the system that ABCL was compiled on: For the [http://common-lisp.net/project/armedbear/release- notes-1.0.1.shtml Recent abcl-1.0.1 release] which was compiled on [http://wiki.openindiana.org/oi/oi_151a+Release+Notes OpenIndiana oi_151a] system one sees: {{{ CL-USER> (asdf::implementation-identifier) abcl-1.0.1-svn-13750-13751-fasl38-solaris-x86 }}} I vaguely remember discussing this with Faré, suggesting the right value might be the current JVM version that ABCL finds itself hosted upon. Patches solicited. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/192> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #34: adjust generated '*.cls' filenames
by armedbear 14 Jul '12

14 Jul '12

#34: adjust generated '*.cls' filenames ------------------------+--------------------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | ------------------------+--------------------------------------------------- dmiles: it be nice to eventually name the coerce-666.cls coerce_666.cls as the same name of the way classpaths think about them (they'd continue to work).. one argument agaist is our autoloader at least gets a better whack at finding them in the right context apart from classloader -- Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/34> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-ticket January 2012