>From Tom
I got what I needed out of it but I think you might want to reconsider
this structure. Using GWT in a chain that long isn't really going to
perform that well, even if it does get compiled and inlined.
I have thought of that ( Charles coverts from GWT to vTable at 5 GWTs
deep) but i
On Aug 31, 2011, at 12:23 PM, Mark Roos wrote:
> Very interesting, I see that I need a hint for the class/method name. ( it
> is the source file name but that doesn't print here)
>
> getNIl/true and false are currently a probe into a hash map but should be a
> static var. I can
> see that
Is that your GWT chains? If so, these are either a little too long or we
have a bug somewhere.
I don't think so ( I think this is a constant look up )
The test part of gwt looks like
public static boolean test(RtObject oldClass, RtObject receiver) {
//System.out.println("test");
/
Very interesting, I see that I need a hint for the class/method name. (
it is the source file name but that doesn't print here)
getNIl/true and false are currently a probe into a hash map but should be
a static var. I can
see that it could get pretty large to inline. There are some other
obj
Tom was looking into a bug with his bimorphic inlining patch and said something
about massive inlining with RtalkTest so I thought I also give it a shot.
One thing I can say for sure: massive inlining and huge methods!
We get a lot like:
@ 115 java.lang.invoke.MethodHandle::asSpreader (13
