Rémi Forax wrote: > > so the VM knows that only methods *DetectingOverflow are able to > throw that specific exception. > int addDetectingOverflow(int x, int y) throws IntegerOverflowException > This also have the advantage that the inlining heuristic can be tweaked > to not count exception handlers that receive that specific exception. > > Generalize this to "UnexpectedTypeStateException" and build that > into a set of patterns that accomplish user-defined deoptimization. > That would be worth special-casing in the JVM. > > -- John_______________________________________________
Would not s specialized GWT be a nice way to handle this? Especially one where the developer could provide a test in an inline assembly like style for slot access, unboxing and compares Seems to me John mentioned an idea for a methodHandle to inline code as in interesting concept mark
_______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
