You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What should the executable be able to do?
I think it should be able take in either a .java file or a .class file (call javac as needed if a .java file) and then with the bytecode it would be able to:
Pretty print the IR (similar to javap -v)
Create a corresponding .class file after having passed through the optimizer
The text was updated successfully, but these errors were encountered:
I've currently written the majority of parts required to convert from .class files to the IR format. The format itself isn't set in stone, and for testing it would probably be easiest if we can parse other formats such as that of krakatau. I was also wondering if we wanted to support parsing javap output, since it looks like they do have enough information to generate classfiles, though not nicely packages. Krakatau's constant pool variant (to generate the same class data) works fine, but isn't as readable, whereas javap's version is readable, but more annoying to parse.
For .java to .class, we'll just rely on javac, since that seems like a much harder problem if you consider validation.
What should the executable be able to do?
I think it should be able take in either a
.java
file or a.class
file (calljavac
as needed if a.java
file) and then with the bytecode it would be able to:javap -v
).class
file after having passed through the optimizerThe text was updated successfully, but these errors were encountered: