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] |
David Daney wrote:
Right, and the JET paper suggests that they know a lot about how all the system classes behave. That might be the key to most of the performance improvement -- you're not alowed to replace system classes, and many of them are final, so...
... Any call to any method in java.* could be inlined or converted into a call to an equivalent but more effecient implementation. Further more, code analysis can be done to see if it is safe to use vastly simpler implementations.
You can only do this if you make some closed-world assumptions. Certainly for things like Math.*, the methods are simple enough and well-defined enough that they can be trivially inlined - and we already do this. But for the general case, its not possible to inline java.* methods without breaking binary compatibility rules, and thus disallowing the code from running on a newer version of the runtime.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |