Mark Wielaard wrote:
The rest of the verify output follows, but I have not analysed it yet.
Cheers,
Mark
Name: verify-jikes.libgcj
verify-jikes.libgcjType: Plain Text
Hi,
On Sat, 2002-02-09 at 10:24, Eric Blake wrote:
Name: verify-jikes.libgcj
It looks like all the errors listed in this file were incompatible type
on stack, in other words, side effects of your ClassLoader hack.
Yeah. Sorry about all the false positives. It did
Eric Blake wrote:
Mark Wielaard wrote:
And this time it actually had a valid VerifyError!
This new jikes is a bit to clever about String concatenations.
I'll fix that today, and repost here when it is up.
I committed that patch to Jikes' CVS earlier today, fixing the
VerifyErrors
Eric Blake [EMAIL PROTECTED] writes:
Eric Blake wrote:
Mark Wielaard wrote:
And this time it actually had a valid VerifyError!
This new jikes is a bit to clever about String concatenations.
I'll fix that today, and repost here when it is up.
I committed that patch to
Hi Eric,
On Thu, 2002-02-07 at 03:50, Eric Blake wrote:
I just committed a patch, after spending all afternoon hacking, that
ensures that the CVS version of jikes will compile Classpath without
failure. I have not tried your verify script to see if all the class
files are valid, but it is
Mark Wielaard wrote:
And this time it actually had a valid VerifyError!
This new jikes is a bit to clever about String concatenations.
I'll fix that today, and repost here when it is up.
--
This signature intentionally left boring.
Eric Blake [EMAIL PROTECTED]
BYU student,
Mark Wielaard wrote:
Hi Eric,
On Mon, 2002-02-04 at 22:44, Eric Blake wrote:
I'm one of the jikes developers. I know that Jikes 1.15 has some
problems compiling inner classes with private constructors, (jikes
compiles with exit status 0, but execution of the resulting .class file
Hi,
On Tue, 2002-02-05 at 22:08, Tom Tromey wrote:
So it would probably be easier to use the verifier in the compiler.
The simplest way, which I use quite a bit, is:
gcj --syntax-only foo.class
Nice. I tried that (with gcj from CVS) for Classpath compiled with jikes
1.15, gcj 3.0.4
Hi,
On Tue, 2002-02-05 at 22:08, Tom Tromey wrote:
Using the runtime verifier in this situation would be hard, because
you'd have to convince libgcj to load the bytecode for various java.*
classes, which are preloaded.
The attached program tries to do it anyway. And I get a lot of verify
Hi,
On Wed, 2002-02-06 at 15:40, Mark Wielaard wrote:
I am going to play a bit more with this to see if I can see were some of
the other errors come from to better understand what libgcj is doing and
wether I am not feeding you completely bogus data.
I changed the program a little bit to
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
Mark I changed the program a little bit to force loading all classes
Mark through the same ClassLoader when possible. Now it actually
Mark seems to work. But a lot of the VerifyErrors seem to be wrong.
There are probably remaining bugs in the
Hi,
On Wed, 2002-02-06 at 20:17, Tom Tromey wrote:
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
Mark I changed the program a little bit to force loading all classes
Mark through the same ClassLoader when possible. Now it actually
Mark seems to work. But a lot of the VerifyErrors seem
Hi,
On Wed, 2002-02-06 at 20:41, Mark Wielaard wrote:
But I have attached the results so far.
I will go through the VerifyErrors I get now to see if they are real.
Reading bytecode makes your head hurt.
java.lang.VerifyError: verification failed at PC 82 in
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
java.lang.VerifyError: verification failed at PC 82 in
java.net.URLDecoder:decode((Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;):
array type expected
Mark This seems to be a bug in the verifier. When you see arraylength the
Mark
Hi Tom,
On Wed, 2002-02-06 at 22:35, Tom Tromey wrote:
Thanks. I've checked in a new test case for this (they are in the
Mauve verify module). Interestingly, gcj crashes on the test case.
I've also written a verifier patch which I am testing. I'll check it
in once that is done.
Wow,
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
Mark I am interested in how your fix looks.
It is basically the same as your fix, except I added a type::isnull()
method.
Tom
___
Classpath mailing list
[EMAIL PROTECTED]
Hi,
On Wed, 2002-02-06 at 20:41, Mark Wielaard wrote:
java.lang.VerifyError: verification failed at PC 37 in
java.util.zip.ZipFile:readEntries(()V): incompatible type on stack
Another bug in the verifier. dup2 actually dups the stack. Patch
attached. Still not found any bugs in jikes.
On Wed, 2002-02-06 at 23:12, Tom Tromey wrote:
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
Mark I am interested in how your fix looks.
It is basically the same as your fix, except I added a type::isnull()
method.
It looks like that does not solve all problems with null arrays.
The
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
java.lang.VerifyError: verification failed at PC 37 in
java.util.zip.ZipFile:readEntries(()V): incompatible type on stack
Mark Another bug in the verifier. dup2 actually dups the stack. Patch
Mark attached. Still not found any bugs in jikes.
Mark Wielaard wrote:
I also tried compiling jikes from CVS but I am unable to compile
Classpath with it. Simple test programs work though. Needs some
debugging. Eric, is jikes from CVS 'stable'?
I just committed a patch, after spending all afternoon hacking, that
ensures that the CVS
Hi,
I downloaded and compiled the whole classpath on the 17 January 2002.
I used jikes 1.12 8/1/2000 which came with the SuSe 7.1 system with
the following options
./configure --prefix=`pwd` --with-jikes --disable-load-library --disable-jni
--disable-cni
The build was successful and I've
Mark Wielaard wrote:
Have people with jikes problems actaully reported them to the jikes
developers? We can try to recompile Wonka with 1.15 to see what happens.
Stuart, what program were you using which forced you to downgrade to
1.14?
We were going to report our main problem with 1.15,
Hi Eric,
On Mon, 2002-02-04 at 22:44, Eric Blake wrote:
I'm one of the jikes developers. I know that Jikes 1.15 has some
problems compiling inner classes with private constructors, (jikes
compiles with exit status 0, but execution of the resulting .class file
causes a VerifyError), and
Mark == Mark Wielaard [EMAIL PROTECTED] writes:
Mark That would be very nice to have. But we need a way to check if
Mark it solves the verify errors. I will spend some time tomorrow to
Mark see how/if we can use the gcj verifier for this.
There are actually two verifiers in gcj -- the one in
Mark Wielaard wrote:
Hi,
The HACKING file says:
- IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
I am using jikes Version 1.15 - 26 Sept 2001 and didn't notice any
errors. Does anybody remember why we don't recommend jikes 1.13?
With Wonka we've had problems with every
Hi,
The HACKING file says:
- IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
I am using jikes Version 1.15 - 26 Sept 2001 and didn't notice any
errors. Does anybody remember why we don't recommend jikes 1.13?
With Wonka we've had problems with every version
John Leuner wrote:
There were issues (don't remember exactly what), but I've been using
the jikes 1.15 in debian/unstable and it seems to work fine. (I have
compiled all of classpath with it)
FWIW, I had to put jikes in debian/unstable on hold at 1.14-0.4 because
it started doing nasty
Hi,
Chris Gray wrote:
With Wonka we've had problems with every version after 1.12.1 (!).
Problems includes: dumps core on valid input, outputs illegal
bytecode
Stuart Ballard wrote:
FWIW, I had to put jikes in debian/unstable on hold at 1.14-0.4 because
it started doing nasty things to my
I'm one of the jikes developers. I know that Jikes 1.15 has some
problems compiling inner classes with private constructors, (jikes
compiles with exit status 0, but execution of the resulting .class file
causes a VerifyError), and there are a few of those in Classpath. I'm
not sure if the
Mark Wielaard wrote:
Have people with jikes problems actaully reported them to the jikes
developers? We can try to recompile Wonka with 1.15 to see what happens.
Stuart, what program were you using which forced you to downgrade to
1.14?
The problems I encountered were in a program written
Mark Wielaard [EMAIL PROTECTED] writes:
OK. So it seems that we can recommend jikes 1.15 for compiling Classpath
but it may have some problems for other applications. I will put that in
the HACKING and INSTALL notices.
There were also problems with compiled constants (final static) using
31 matches
Mail list logo
