[patch] compiling multiple Java source files at once
Alexandre Petit-Bianco
apbianco@cygnus.com
Mon Feb 19 17:22:00 GMT 2001
Per Bothner writes:
> The gcj patches also support multiple .class files on the command
> line, but jc1 may be unable to find the right classes.
OK, here's something I came accross:
$ cat X.java
$ gcj -C X.java
$ gcj *.class --main=X
X.java: In class `Y':
X.java: In method `()':
X.java:0: verification error at PC=4
X.java:0: falling through end of method
I had a look and it seems that byte_ops contains nothing but
nops. Would that be a problem with jcf?
By the way, when I wanted to start debugging, and I did this:
$ gcj -v *.class
And I got:
...
/home/apbianco/install/egcs/install-x86/lib/gcc-lib/i686-pc-linux-gnu/2.97/jc1 /tmp/ccpFSQw2jx -fno-use-divide-subroutine -fuse-boehm-gc -fasynchronous-exceptions -quiet -dumpbase ccpFSQw2jx -g1 -version -ffilelist-file -o /tmp/ccgg2WDU.s
GNU Java version 2.97 20010208 (experimental) (i686-pc-linux-gnu)
compiled by GNU C version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release).
...
I think that `-v' should report something that we can reuse right
away, especially in debug situation (I don't know how many times I
couldn't reproduce a bug unless all flags generated by gcj were passed
to jc1, say, within gdb.) We should keep the filelist file around, but
that would pollute /tmp. Could we instead create the filelist in the
user's home directory when `-v' is used?
./A
More information about the Gcc-patches
mailing list