2004
DOI: 10.1007/978-3-540-30124-0_22
|View full text |Cite
|
Sign up to set email alerts
|

A Functional Scenario for Bytecode Verification of Resource Bounds

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0

Year Published

2004
2004
2010
2010

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 16 publications
(33 citation statements)
references
References 12 publications
0
33
0
Order By: Relevance
“…However, the system assumes that source programs come from a first-order functional language with a resource-aware type system [19]. Similarly, Amadio et al [4] defined a simple stack machine for a first-order functional language and showed how to perform type, size and termination verifications at the bytecode level. Their main result is a proof that each program with the quasi-interpretation property 1 that terminates has a polynomial stack bound.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, the system assumes that source programs come from a first-order functional language with a resource-aware type system [19]. Similarly, Amadio et al [4] defined a simple stack machine for a first-order functional language and showed how to perform type, size and termination verifications at the bytecode level. Their main result is a proof that each program with the quasi-interpretation property 1 that terminates has a polynomial stack bound.…”
Section: Related Workmentioning
confidence: 99%
“…Recent works [19,21] are mostly based on analysing functional programs where the presence of immutable data structures makes such analysis easier to formalise. Even though [5,4] are targeted at Java-based bytecode programs, their frameworks again assume that bytecode programs are compiled from first-order functional programs. Other works, such as [13,28], merely provide a framework for checking that the memory usage of object-oriented programs conform to user-supplied memory specifications either through static analysis or runtime checking.…”
Section: Introductionmentioning
confidence: 99%
“…The scheduler owns three registers: (1) tid that stores the identity of the current thread, (2) time for the current time, and (3) wtime for the last time the store was modified. The notion of time here is of a logical nature: time passes whenever the scheduler transfers control to a new thread.…”
Section: Schedulermentioning
confidence: 99%
“…Property ReadOnce is a transposition of the read once condition (Section 2.1) at the level of the bytecode. In [1], we have presented a method to perform resource control verifications at bytecode level. This work is just concerned with the functional fragment of our model.…”
Section: Control Flow Analysis Revisitedmentioning
confidence: 99%
“…Works [1], [2] are mostly aiming to analyze functional programs where the immutable data structures make such analysis easier to formalize. The works [3], [4] target at Java-based Bytecode programs, but their frameworks again assume that Bytecode programs are compiled from functional programs without mutability and assignments. Other works, e.g.…”
Section: Introductionmentioning
confidence: 99%