You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mikhail Loenko (JIRA)" <ji...@apache.org> on 2007/03/12 11:57:09 UTC

[jira] Updated: (HARMONY-3363) [DRLVM] contribution of alternative bytecode verifier

     [ https://issues.apache.org/jira/browse/HARMONY-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Loenko updated HARMONY-3363:
------------------------------------

    Attachment: Verifier_patched.zip

> [DRLVM] contribution of alternative bytecode verifier
> -----------------------------------------------------
>
>                 Key: HARMONY-3363
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3363
>             Project: Harmony
>          Issue Type: New Feature
>          Components: Contributions
>            Reporter: Mikhail Loenko
>         Attachments: Verifier_bulk.zip, Verifier_patch, Verifier_patched.zip
>
>
> 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

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.