This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
The
construction of the binary compatibility/link tables would be completed
before any code from a given class is run, so there arn't any issues
with having to synchronize & check link tables at runtime. (the
statement in my post above should actually read "java.lang.Class
objects would be created at runtime as classes are _linked_ ")
Creating class instances on the heap could go a long way towards solving
the large root set problem.
Drifting off topic slightly, I think it does matter when exactly classes
are linked. If I have a class A:
class A { B b() { return new B(); } }
should "new A()" cause B to be loaded? (With the JRE it does not.)
This is an example of what blocks us from using gcj from "real world" applications.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |