New JIT

[Peter Mehlitz]

Well, memory consumption *is* a problem with Swing, but I don't think you can
win with respect to "field packing", which would come with tremendous side
effects. Even if the number of swing objects is huge (more than 1000 of them
in SwingSet), and these objects tend to be big, the main memory consumption is
caused by three different reasons: (a) the amount of involved code (> 1.5 M
for SwingSet), (b) extensive use of images, and (c) heap traffic
(number/frequency of very short living objects for returns, parameters).

-- Peter