
| Key: |
RVM-152
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Peter Donald
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
We should introduce a byte code verifier. This should ideally support the verification of class files with versions up to 1.5 and it should support the alternative verification mechanism introduced in JSR 202. One alternative is to use verifiers from projects such as justice from BCEL or we could wait until the Moxie codebase is released and reuse that verifier.
|
|
Description
|
We should introduce a byte code verifier. This should ideally support the verification of class files with versions up to 1.5 and it should support the alternative verification mechanism introduced in JSR 202. One alternative is to use verifiers from projects such as justice from BCEL or we could wait until the Moxie codebase is released and reuse that verifier. |
Show » |
|
i.e. For intra-procedural constraints we could add rules to ensure;
For inter-procedural constraints we could add rules like
In the future we could also add all sorts of annotations and verify them. (Using Haskells naming mechanisms)
We could also use the "verifier" to automagically classify different procedures as @IO, @Pure, @STM etc which would simplify the compiler and enable many more optimizations with relatively minimal overhead (as data flow analysis already donw within verifier).