#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
#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
#222: Deprecate Debug.assertXXXX()
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone: 1.2.0
Component: java | Version:
Keywords: |
------------------------+---------------------------------------------------
Long term: move all occurrances to (meaningful) lisp conditions.
Rationale: Statements should never call System.exit(); we're a library and
should allow callers to free resources instead of breaking out hard.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/222>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#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
#217: ANSI tests wont run on Revision 14011: /trunk/abcl
----------------------------------------------------------------------------------------------+
Reporter: https://www.google.com/accounts/o8/id?id=aitoawmy4u2arai5whm4pn4h0biwcvdnd3… | Owner: ehuelsmann
Type: defect | Status: new
Priority: major | Milestone: 1.1.0
Component: build | Version: 1.1.0-dev
Keywords: |
----------------------------------------------------------------------------------------------+
Steps to reproduce:
mkdir reproduce
cd reproduce
svn co -r 14011 svn://common-lisp.net/project/armedbear/svn/trunk/abcl
abcl
svn co svn://common-lisp.net/project/ansi-test/svn/trunk/ansi-tests ansi-
tests
cd abcl
ant test.ansi.interpreted # or test.ansi.compiled
Result:
[java] ; redefining REGRESSION-TEST:DO-EXTENDED-TESTS in
#P"C:/development/ansi-tests/rt.lsp" (previously defined in
#P"C:/development/abcl-ikvm/vanila/ansi-tests/rt.lsp")
[java]
[java]
[java] Caught UNBOUND-SLOT while processing --eval option
"(asdf:operate (quote asdf:test-op) :ansi-interpreted)":
[java] The slot NAME is unbound in the object #<SHORT-METHOD-
COMBINATION {1346E527}>.
[java] Invalid initarg :NAME in call to MAKE-INSTANCE with arglist (#<
[java] ; Compilation unit finished
[java] ; Caught 31 STYLE-WARNING conditions
[java]
[java] Java Result: 2
[echo] Finished recording test output in abcl-test-20124517-0145.log.
Expected result:
The ANSI tests to run
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/217>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#218: More Compreshensive Regression testing
----------------------------------------------------------------------------------------------+
Reporter: https://www.google.com/accounts/o8/id?id=aitoawmy4u2arai5whm4pn4h0biwcvdnd3… | Owner: ehuelsmann
Type: enhancement | Status: new
Priority: minor | Milestone: 2.0
Component: interpreter | Version: 1.1.0-dev
Keywords: |
----------------------------------------------------------------------------------------------+
There are two types of ANSI tests.. Interpreted and Complied.
(ansi.interpred and ansi.compiled)
There are also two ways to run ABCL
1) "abcl library compiled" - abcl.compiled
currently the way it is compiled into abcl.jar
2) "abcl library interpreted" - abcl.interpreted
the abcl.jar or classpath contains only .lisp files
this means it contains no "class or ABCL files"
So this means ABCL can run ANSI tests in four modes:
I) abcl.interpreted.ansi.interpreted
II) abcl.compiled.ansi.interpreted
III) abcl.interpreted.ansi.compiled
IV) abcl.compiled.ansi.compiled
The old maintainer started out only able to run I and III before ABCL had
a compiler. This is why there is so much "Java code".
(Not to be confused with some new goal "just enough java code to get the
system able to compile itself")
As time went on (as ABCL's compiler was implemented) II and IV can now be
ran. With various failures being different and giving guidance to what to
fix in the "compiler" or "Lisp code" when comparing all four modes.
Currently now we only run II and IV.
This ticket is an enhancement request to begin running ABCL in all four
modes.
This I believe will help spot what "java code" really can be removed and
what can be removed safely.
Although the new goal "just enough java code to get the system able to
compile itself" is admirable, I think we should still work to support low
regressions in modes I and III AND still reduce the "Java code"
Though, I'd like all 4 modes to be ran I haven't created the patch to help
us build ABCL in such a method as to make this possible yet. If someone
knows how, please do so. If not, I'll get around to it.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/218>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#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