Re: Compiling with jikes 1.13

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

Re: nio package and asynchronous io

I'd be happy to contribute stuff (see earlier ps remark about swing stuff) And yup, dislike typing docs. but I guess that's been noticed. Ps, yup, just yesterday people came by submitting compiler construction assignments for me to test who were also working on the dot-gnu thing ! R. Mark

Re: Compiling with jikes 1.13

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

Re: Compiling with jikes 1.13

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

Re: Compiling with jikes 1.13

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

Re: Compiling with jikes 1.13

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

Re: Compiling with jikes 1.13

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

build question

I'm trying to do a completely fresh build of classpath with the latest CVS version of Jikes, to see what needs to be fixed in Jikes (or what workarounds need to be patched into classpath) by Friday. But during the autoreconf stage, I was getting: $ automake native/jni/java-lang/Makefile

Re: Compiling with jikes 1.13

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

Re: build question

Hi, On Wed, 2002-02-06 at 21:18, Eric Blake wrote: $ automake native/jni/java-lang/Makefile automake: native/jni/java-lang/Makefile.am: `\' is not a standard libtool library name native/jni/java-lang/Makefile.am:15: invalid unused variable name: `libjavalang_la_LIBADD'

Re: build question

Mark Wielaard wrote: Hi, What version of automake are you using? You will need automake 1.5 to build Classpath from CVS (see HACKING). automake 1.5, as bundled in cygwin under their automake-devel branch. I'm not sure if the cygwin developers have done anything on top of the stock

Re: build question

Hi, On Wed, 2002-02-06 at 21:33, Eric Blake wrote: What version of automake are you using? You will need automake 1.5 to build Classpath from CVS (see HACKING). automake 1.5, as bundled in cygwin under their automake-devel branch. I'm not sure if the cygwin developers have done

Re: Compiling with jikes 1.13

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

Re: build question

Eric Blake [EMAIL PROTECTED] writes: Is it ok to commit this patch? Then I can actually do a build to report on the status of jikes/classpath. It's okay to make that change. Clearly something is wrong with the cygwin automake, or with textmode/binmode and the file, but you shouldn't let it

Re: build question

Eric == Eric Blake [EMAIL PROTECTED] writes: Eric automake: native/jni/java-lang/Makefile.am: `\' is not a standard Eric libtool library name This is curious. This error shouldn't happen. Apparently what is happening here is that automake thinks that the `\' continuation character in the

Re: Compiling with jikes 1.13

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,

Re: Compiling with jikes 1.13

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]

Re: Compiling with jikes 1.13

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.

Re: NEWS file for next release

Mark Wielaard wrote: - There seems to be a gcc compiler bug that makes the following patch necessary: --- orp-1.0.9/base_natives/common_olv2/mon_enter_exit.cpp +++ orp/base_natives/common_olv2/mon_enter_exit.cpp @@ -294,7 +294,7 @@ #else nop;nop;nop

Re: Compiling with jikes 1.13

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

Re: Compiling with jikes 1.13

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.

Re: Compiling with jikes 1.13

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