From: Peter Lane <peter@peterlane.info>
To: kawa@sourceware.org
Subject: Re: limit in number of srfi-64 tests
Date: Sat, 06 May 2017 18:04:00 -0000 [thread overview]
Message-ID: <dd86e1bd-eca2-73a2-0fd8-cdf6e153c7b9@peterlane.info> (raw)
In-Reply-To: <50e14906-2056-8e92-8450-8a27b5012074@peterlane.info>
On 06/05/17 12:47, Peter Lane wrote:
> I have found what appears to be a limit in the number of tests that can
> be used in a srfi 64 test file. Attached is a simple example merely
> consisting of multiple (test-equal 1 1) statements.
There's a workaround to this (as Per let me know). Use the -f switch
and it works (for srfi 64 tests at least, which can be handled
line-by-line).
$ kawa -f many-tests.sps
>
> With the 560 tests in the file I get an error:
>
> $ kawa --version
> Kawa 2.4 (git describe: kawa-2.3-30-gdad3755-dirty)
> Copyright (C) 2017 Per Bothner
>
> $ kawa many-tests.sps
> Exception in thread "main" java.lang.ClassFormatError: Invalid method
> Code length 65548 in class file many-tests
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:760)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:642)
> at gnu.bytecode.ArrayClassLoader.loadClass(ArrayClassLoader.java:127)
> at gnu.expr.ModuleExp.evalToClass(ModuleExp.java:133)
> at gnu.expr.ModuleExp.evalModule1(ModuleExp.java:245)
> at kawa.Shell.compileSource(Shell.java:587)
> at kawa.Shell.runFile(Shell.java:555)
> at kawa.Shell.runFileOrClass(Shell.java:468)
> at kawa.repl.processArgs(repl.java:700)
> at kawa.repl.main(repl.java:820)
>
> If I uncomment one test, it runs fine:
>
> $ kawa many-tests.sps
> %%%% Starting test many tests (Writing full log to "many tests.log")
> # of expected passes 559
>
> It appears the bytecode output has hit a Java limitation.
>
--
Peter Lane
http://peterlane.info
parent reply other threads:[~2017-05-06 18:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <50e14906-2056-8e92-8450-8a27b5012074@peterlane.info>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd86e1bd-eca2-73a2-0fd8-cdf6e153c7b9@peterlane.info \
--to=peter@peterlane.info \
--cc=kawa@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).