-
-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any plans to support the Vector API? #380
Comments
Hi @Ledmington if you look in jitwatch.out log file you will see that the current version of JITWatch is unable to parse classes it cannot find. This is the cause of several reported issues and goes back to a poor design decision made long ago when I used classloading as a way of building the class and method model. I have a new open source project https://github.com/chriswhocodes/ClassAct which is a basic binary classfile parser that does not use the classloader. Once I replace the existing JITWatch classfile parser with ClassAct then it will be able to support code like this example that uses internal APIs. I'm hoping I will find time to do this work soon. Kind regards, Chris
|
Wouldn't it be better to use the new ClassFile API instead? |
Hi @Thihup Exactly, I have no control over when ClassFile API becomes available and it won't work with older Java versions. Mine is compatible with JDK8+ and I can tailor the API to its consumers (JITWatch and https://byte-me.dev). I think those are worth the effort of keeping up with the fairly minor changes in new Java versions :) |
I'm sorry but I don't understand. If the current version of JITWatch uses the class loader to parse classes, shouldn't it be able to parse the Anyway, I'm willing to help with your ClassAct project, if needed. |
Right now, if you write a simple loop using the Vector API like this:
JitWatch will show you nothing: not even the source code or the bytecode.
Do you have any plans to support it?
The text was updated successfully, but these errors were encountered: