G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. In Proc. 12th Euromicro Intl. Conf. on Real-Time Systems, Stockholm, June 2000.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....runtime, its bytecode can rst be analyzed to determine how often each instruction is invoked. This bytecode analysis essentially consists in executing the operator with a set of sample parameters and recording how often each instruction is executed. For more insight into the problem, see e.g. [5]. The obtained number and sequence of invocations can then be used to predict the runtime of the operator using a timing model for the server machine. At the moment, timing models in our system simply consist of a table with previously measured runtimes for each instruction type, which are ....

....systems, prediction of execution time for sequential code (known as worst case execution time analysis) has been an active area of research for many years (e.g. 1] However, the analysis of portable code, such as Java bytecode, has not been studied until recently. Initial research e orts [3, 5] are concerned with the high level analysis of bytecode, i.e. the problem of counting how often an instruction is executed in the worst case (mentioned only brie y in Section 5 of this paper) The concrete time values for single instructions are assumed to be given in form of a machine model . ....

G. Bernat, A. Burns, and A. Wellings. Portable worst case execution time analysis using java byte code. In Proc. 12th EUROMICRO conference on Real-time Systems, June 2000.

....running on modern hardware or compiled using optimizing compilers, since the time for each operation will in these cases depend on its context. This is similar to the problems encountered with the early timing schema approach [PS90] Bernat et. al performs WCET analysis on the Java Byte code [BBW00] level. Their method is easily portable between different target platforms but encounters similar effectivity problems as the source code WCET analysis methods mentioned above. Petters and Farber [PF99] perform sophisticated measurements of programs running on target hardware, aided by static ....

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis using Java Byte Code. In Proc. of the 12 th Euromicro Workshop of Real-Time Systems, pages 81--88, 2000.

....Park [27] and Bernat [4] used explicit annotations to identify false paths. Lundqvist [22] used instruction level symbolic execution for path analysis. Liu and Gomez [18] used similar techniques (on the source code level) to determine loop bounds, recursion depths, and false paths. Altenbernd [2] used a related approach to exclude false paths. Several of the WCET analysis techniques just mentioned can be categorized as symbolic execution (or abstract interpretation) of the program. In this context, such symbolic execution differs from ordinary execution in that variables may assume the ....

....The Sknerost environment is currently under implementation; that work continues. References [1] M. Alt, C. Ferdinand, F. Martin, and R. Wilhelm. Cache Behavior Prediction by Abstract Interpretation. Proceedings of the International Static Analysis Symposium (SAS 96) LNCS 1145, Springer, 1996. [2] P. Altenbernd. On the False Path Problem in Hard Real Time Programs. Proceedings of the 8th Euromicro Workshop on Real Time Systems, 1996. 3] N. M. Al Yaqoubi. Reducing Timing Analysis Complexity by Partitioning Control Flow. Master s Thesis, Department of Computer Science, Florida State ....

[Article contains additional citation context not shown here]

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. To appear in Proceedings of the 12th EuroMicro Conference on Real-Time Systems, Stockholm, June 2000.

No context found.

G. Bernat, A. Burns, and A.J. Wellings, "Portable Worst-Case Execution Time Analysis Using Java Byte Code", Proceedings of the 12th EuroMicro Conference on Real-Time Systems, Stockholm, June 2000

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. In proc. 6th Euromicro conference on Real-Time Systems, pages 81--88, June 2000.

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. Proceedings of the 6th Euromicro Conference on Real-Time Systems, pages 81--88, June 2000.

....the dynamic dispatching issues in WCET analysis can be addressed with minimum annotations to estimate safe and tight WCET bounds for hard real time applications in [14] 3. 1 Portable WCET Analysis A portable WCET analysis approach based on the Java architecture has been proposed by Bernat et al. [3, 2]. This section presents how portable WCET analysis can be adapted for our environment [16] Portable WCET analysis uses a three step approach: highlevel analysis, which analyses the annotated Java class files and computing the portable WCET information in the form of Worst Case Execution ....

....at compilation, and run time supported reclaiming that can be carried out at the target platform. Here, we assume that the WCET values or WCEF vectors of each basic block have been calculated. They may be produced while performing static timing analysis by combining the portable WCET analysis [2, 3] and our previous approach [14, 15] Then the WCET value or WCET vector of each basic block can be stored in the XAC format in either separate files or code attributes in JCF files. Note also that the gain time reclaiming graphs can be provided in the XAC format. In addition, the worst case ....

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. Proceedings of the 6th Euromicro Conference on Real-Time Systems, pages 81--88, June 2000.

....in mind: from the design phase to run time phases. For example, using our approach, the system can be evaluated during the design, and the timing constraints of the application can be validated during run time. We integrate our approach with portable WCET analysis, proposed by Bernat et al. [3] and extended by Bate et al. 2] for the WCET estimation. The portable WCET analysis uses a three step approach: high level analysis (i.e. analysing the Java programs) low level analysis (i.e. performing platform dependent analysis on Java byte code instructions implemented for the target ....

G. Bernat, A. Burns, and A. Wellings. Portable WorstCase Execution Time Analysis Using Java Byte Code. In proc. 6th Euromicro conference on Real-Time Systems, pages 81--88, June 2000.

....A customised tool may be developed that incorporates all the rules and guidelines (see Appendix A of [23] and throughout this paper. Such a tool may also be able to obtain the Worst Case Execution Time (WCET) and worst case memory consumption of each thread, thus enabling schedulability analysis [6, 18]. Standard Java tools or model checkers, such as ESC Java [24] and Java Pathfinder 2 [9, 21] may be used, as well. 6. AN EXAMPLE PROGRAM We present a simple and naive traction control system that senses any difference between the front and rear wheel spin speeds, and reduces the engine output ....

G. Bernat, A. Burns, A. Wellings, Portable Worst Case Execution Time Analysis using Java Bytecode, In EUROMICRO conference on RealTime Systems, 2000.

....is initially made on the programming language used to generate such code, neither availability of the source code is required. We have previously shown that control flow and data flow information can be extracted from the JCF and therefore source language independent WCET analysis can be performed [4]. Current techniques for WCET analysis can not be directly applied to this portable framework. This is mainly because the high level analysis stage does not have available the execution time of individual code segments. For this reason the high level analysis uses the notion of WCEF vectors as ....

....goes in at the first instruction and leaves through the last one way which compensate for the added benefits that portability brings. The work presented in this paper is an investigation of a portable WCET framework based on the Java Platform and is an extension of the contributions presented in [4] and [7] There are currently two projects for defining the requirements of real time extensions of the Java Platform. The Real time core extensions for the Java Platform (or Core for short) by the J consortium [2] and the Real Time Specification for Java by the Real time for Java expert group ....

[Article contains additional citation context not shown here]

G. Bernat, A. Burns, and A. Wellings, "Portable worst case execution time analysis using java byte code," in proc. 6th EUROMICRO conference on Real-time Systems, pp. 81--88, June 2000.

No context found.

G. Bernat, A. Burns, A. Wellings, Portable Worst Case Execution Time Analysis using Java Bytecode, In Proceedings of the 12 EUROMICRO conference on Real-Time Systems, 2000.

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis Using Java Byte Code. In Proc. 12th Euromicro Intl. Conf. on Real-Time Systems, Stockholm, June 2000.

No context found.

Bernat, G., Burns, A., and Wellings, A. Portable worst case execution time analysis using Java byte code. In Proceedings of the 12th EUROMICRO Conference on Real-time Systems, June 2000.

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis using Java Byte Code. In In Proceedings of the 6th International EUROMICRO conference on Real-Time Systems, Stockholm, June 2000.

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable WorstCase Execution Time Analysis using Java Byte Code. In Proceedings of the 6th International EUROMICRO conference on Real-Time Systems, Stockholm, June 2000.

No context found.

G. Bernat, A. Burns, and A. Wellings. Portable Worst-Case Execution Time Analysis using Java Byte Code. In In Proceedings of the 6th International EUROMICRO conference on Real-Time Systems, Stockholm, June 2000.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC