[HARMONY-3363] [DRLVM] contribution of alternative bytecode verifier

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Contributions
• Patch Info: Patch Available
• Assignee: Mikhail Loenko
• Reporter: Mikhail Loenko
• Created: 12/Mar/07 10:54
• Updated: 02/May/13 02:29
• Resolved: 24/Jul/07 04:56

Description

This is contribution of experimental bytecode verifier on behalf of Intel.

"Experimental" means that there is no formal proof currently available of its equivalence to the step-by-step verification algorithm described in the spec.

The only known difference to the conventional verifier is dead code verification: RI makes stricter checks against dead code.
Since it's about dead code, this difference does not affect vulnerability

Comparing to the current Harmony verifier, this one is supposed to be complete (Harmony currently does not support jsr/ret verification) and much faster

So, I'm attaching 3 files:

The first one: Verifier_bulk.zip is a bulk contribution on behalf of Intel for archiving purposes. It contains the legal files as well

The second one: Verifier_patch is my fix to the bugs that I found while the first archive was coming thru legal

The third archive Verifier_patched.zip is a merge for previous two. It's an up-to-date version for all the engineering purposes

To try it out one should replace the current 'verifier' directory in vm with the new one and rebuild

Issue Links

• is depended upon by: HARMONY-4409 [drlvm][verifier] Harmony throws VerifyError (Incompatible argument for function) on generics/varargs specific bytecode while RI doesn't