| Y. Ishikawa, H. Tokuda, and C. Mercer. Object-Oriented Real-Time Language Design: Constructs for Timing Constraints. In Proceedings of the ACM Object-Oriented Programming: Systems, Languages and Applications, pages 289--296, October 1990. |
....try to ease the task of estimating the number of general loop iterations by forbidding general loops, i.e. by forcing the user to supply constant upper bounds for the number of iterations. Another approach is to let the user specify a time bound within the loop has to complete (cf. e.g. [12]) In any case the user, i.e. the programmer, has to react to such exceptional cases. In this paper we will follow a different approach: We will narrow the gap between general loops and for loops by defining discrete loops. These loops are known to complete and are easy to analyze (especially ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object-oriented real-time language design: Con- structs for timing constraints. In ECOOP/OOPSLA '90 Proceedings, pages 289-298, October 1990.
....used in the development of real time systems for quite some time. Research literature has shown that the concept of objects in real time systems is useful. Object oriented real time (OORT) system models such MO2 [1] evaluation taxonomy such as in [2] object oriented real time language design [3, 4], concurrency exploitation in OORT systems using metrics driven approach [5] checking time constraints [6] and verification of function and performance for OORT systems [7] are some of the recent work on applying object oriented technology to real time system design. Although object oriented ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer, "Object-oriented real-time language design: constructs for timing constraints", ACM SIGPLAN Notices, ECOOP/OOPSLA'90 Proceedings, Vol. 25, pp.289-298, Oct. 1990.
....the following subsections several different approaches to real time objects will be reviewed. 1.3. 1 Object Oriented Languages for Real Time The first attempts to enhance an object oriented language, namely C , to become real time capable were the presentations of FLEX [Lin88, Ken94] and RTC [Ish90]. These languages contain special constructs for defining deadlines, periods, and synchronization conditions. Some of these constructs can be mapped to scheduler level abstractions, like task deadlines and priorities. The expressiveness of these language add ons is limited (e.g. RTC provides no ....
Y. Ishikawa, H. Tokuda, C.W. Mercer, Object-Oriented Real-Time Language Design: Constructs for Timing Constraints, Proc. ECOOP/OOPSLA '90, Oct. 1990.
....helps achieve real time correctness and schedulability for the entire system. For this reason we call the transformation real time task slicing. The Language of Time Constrained Events. TCEL s annotation syntax is quite similar to that found in other experimental real time languages (e.g. [17, 19, 21, 24, 27, 38]) However, the semantics differs significantly, in that it is based on the time constrained relationships between observable events. For example, consider a construct such as every 10ms do B, where the block of code B is executed once every 10ms. The typical approach is to establish timing ....
Y. Ishikawa, H. Tokuda, and C. Mercer. Object-oriented real-time language design: Constructs for timing constraints. In Proceedizgs of OOPSLA-90, pages 289 298, October 1990.
....and hand optimization. Additional measures may include re coding key subsystems in assembly language, off loading functions in programmable logic, or perhaps redesigning the system altogether. Several programming languages help manage the requirements side of the design equation; examples are [13, 17, 19, 23, 27]. These languages provide programmers with a convenient means of postulating timing constraints within a program s text. The constraints are, in turn, conveyed to the real time scheduler as a directive, or perhaps replaced by kernel calls to be invoked at runtime. In this paper we present an ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object-oriented real-time language design: Con- structs for timing constraints. In Proceedings of OOPSLA-90, pages 289 298, October 1990.
....are not suitable for capturing the end to end behavior of the systems. In general, the developer (and the user) of a distributed real time application is interested in end to end timing considerations [12] The purely local timing behavior of an object, as expressed by timing annotations such as [9], is not sufficient when the overall system behavior caused by interactions between different object has to be considered. Thus, an abstraction for the monitoring of end to end behavior has to be introduced. A good example of a monitoring tool providing a breakdown of an end to end abstraction is ....
Y. Ishikawa, H. Tokuda, C.W. Mercer: "ObjectOriented Real-Time Language Design: Constructs for Timing Constraints", ECOOP/OOPSLA '90 Proceedings, October 1990.
....been derived (cf. e.g. KU76, KU77] and a large number of algorithms has been developed (cf. e.g. AC76, GW76, HU77, Sre95, SGL98, Tar81a, Tar81b] See [MR90, RP86] for an overview. Worst Case Execution Time (WCET) analysis does not have such a long standing tradition (cf. e.g. CBW96, HS91, ITM90, NP93, Par93, PK89, PS97, Sha89] Designers of real time programming languages usually restrict language features in order to make it possible to guarantee time bounds and introduce new language features to let the programmer add extraneous information on the algorithms which cannot be ....
....they cannot be employed for every data flow framework. 3. A Data Flow Framework for Simple WCET In this section we define a simple data flow framework for worst case execution time analysis. The idea is based on methods for WCET analysis widely used in literature, e.g. PK89, Sha89, HS91, ITM90, GR91] In general, WCET analysis has to deal with two problems # : 1. Determine the timing behavior of if then else statements. 2. Determine the number of loop iterations. Our simple approach handles case (item 1) by defining that (roughly speaking) the WCET of an if then else statement is equal ....
[Article contains additional citation context not shown here]
Yutaka Ishikawa, Hideyuki Tokuda, and Cli#ord W. Mercer, Object-oriented real-time language design: Constructs for timing constraints, ECOOP/OOPSLA '90 Proceedings, October 1990, pp. 289--298. 1, 7, 21
....Program [21] Walker, D. Calculus Semantics of Object Oriented Programming Languages, Proceedings of Theoretical Aspects of Computer Software 91, LNCS 526, p532547, Springer Verlag, 1991. 22] Wegner, P. Concepts and Paradigms of ObjectOriented Programming, ACM OOPS Messenger, Vol.1, No.1, August, 1990. 23] Yi, W. CCS Time = an Interleaving Model for Real Time Systems, Proceedings of ICALP 91, LNCS 510, p217 228, 1991. 24] Yonezawa, A. and Tokoro, M. ed) Object Oriented Concurrent Programming, MIT Press, 1987. Appendix In this appendix we show a sketch of an analysis of a real time ....
....Computer Software 91, LNCS 526, p532547, Springer Verlag, 1991. 22] Wegner, P. Concepts and Paradigms of ObjectOriented Programming, ACM OOPS Messenger, Vol.1, No.1, August, 1990. 23] Yi, W. CCS Time = an Interleaving Model for Real Time Systems, Proceedings of ICALP 91, LNCS 510, p217 228, 1991. 24] Yonezawa, A. and Tokoro, M. ed) Object Oriented Concurrent Programming, MIT Press, 1987. Appendix In this appendix we show a sketch of an analysis of a real time program described in R T . We consider a reader writer problem program as shown in Figure 11. This program is ....
[Article contains additional citation context not shown here]
Ishikawa, Y., Tokuda, H., and Mercer, C.W., Object-Oriented Real-Time Language Design: Construction for Timing Constraints, Proceeding of ECOOP/OOPSLA'90, 1990.
....[22, 24] is based on interactions with active entities. The concept of concurrent object orientation is considered as a powerful methodology to design and implement real time systems. Recently, many real time programming languages have been proposed based on this concept, for example see [8, 19]. Real time systems need to meet certain time constraints. The correctness of programs for real time systems depends not only on the functionally behav # Partially supported by JSPS Fellowships for Japanese Junior Scientists Also with Sony Computer Science Laboratory Inc. 3 14 13 ....
Ishikawa, Y., Tokuda, H., and Mercer, C.W., ObjectOriented Real-Time Language Design: Construction for Timing Constraints, Proceeding of ECOOP /OOPSLA'90, 1990.
....This is because concurrent object oriented systems consists of objects which are logically self contained active entities that cooperate with each other. Concurrent objects can model such active elements directly. Recently some real time systems and languages use this concept as their basis [5, 9]. Real time systems have certain time constraints which must be satisfied. The correctness of a real time system depends not only on the logical results of computation, but also on the time at which the results are produced. Therefore, the construction and debugging of real time programs is far ....
Ishikawa,Y., Tokuda,H., and Mercer,C.W., Object-Oriented Real-Time Language Design: Construction for Timing Constraints, In proceedings of ECOOP/OOPSLA'90, 1990.
....a compile time guarantee. For example, RTC [17] is a real time concurrency system designed on this principle. In RTC, timing constraints for behaviours are expressed as temporal scopes, and scoping is achieved by block statements which are inserted in C code. Real Time Concurrent C [18] and RTC [19] are similar systems. The latter supports fine grained constraints by allowing them on individual statements, but they are enforced only at run time, and failure is handled by an exception mechanism. In FLEX [20] timing constraints are specified by constraint blocks which identify constraints to ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object-oriented real-time language design: Constructs for timing constraints. Technical Report CMU-CS-90-111, CarnegieMellon University, March 1990.
....1977; Sreedhar, 1995; Sreedhar et al. 1998; Tarjan, 1981a; Tarjan, 1981b) See (Marlowe and Ryder, 1990; Ryder and Paull, 1986) for an overview. Worst Case Execution Time (WCET) analysis does not have such a long standing tradition (cf. e.g. Chapman et al. 1996; Halang and Stoyenko, 1991; Ishikawa et al. 1990; Nirkhe and Pugh, 1993; Park, 1993; Puschner and Koza, 1989; Puschner and Schedl, 1997; Shaw, 1989) Designers of real time programming languages usually restrict language features in order to make it possible to guarantee time bounds and introduce new language features to let the programmer add ....
....framework. 3. A Data Flow Framework for Simple WCET In this section we define a simple data flow framework for worst case execution time analysis. The idea is based on methods for WCET analysis widely used in literature, e.g. Puschner and Koza, 1989; Shaw, 1989; Halang and Stoyenko, 1991; Ishikawa et al. 1990; Gehani and Ramamritham, 1991) In general, WCET analysis has to deal with two problems 3 : 1. Determine the timing behavior of if then else statements. 2. Determine the number of loop iterations. Our simple approach handles case (1) by defining that (roughly speaking) the WCET of an ....
[Article contains additional citation context not shown here]
Ishikawa, Y., H. Tokuda, and C. W. Mercer: 1990, `Object-oriented real-time language design: Constructs for timing constraints'. In: ECOOP/OOPSLA '90 Proceedings. pp. 289--298.
....is because concurrent object oriented systems consist of objects which are logically self contained active entities that cooperate with each other. Concurrent objects can naturally model such active elements directly. Recently, some real time systems and languages use this concept as their basis [9, 21]. Real time systems have certain time constraints which must be satisfied. The correctness of a realtime system depends not only on the logical results of computation, but also on the time at which the results are produced. Therefore, the construction and debugging of real time programs is far ....
Ishikawa, Y., Tokuda, H., and Mercer, C. W., Object-Oriented Real-Time Language Design: Construction for Timing Constraints,In proceedings of ECOOP/OOPSLA'90, 1990.
....occurs to enable its survival This is the notion of least suffering. DROL is implemented as an extension of C with the capability of describing temporal constraints, running on a distributed real time operating system, called the ARTS kernel [11] The syntax of DROL is an extension of RTC [2], the useful real time notations of which DROL inherits. The DROL compiler translates a program written in DROL into C codes including interfaces for the ARTS kernel. DROL has the following features: ffl In addition to C objects, DROL can define active objects that are multiple threaded ....
....following features: ffl In addition to C objects, DROL can define active objects that are multiple threaded objects and which are defined with timing information such as the timing constraints for each method. This notion of active object is as same as that of RTC proposed by Ishikawa in [2]. ffl It supports two types of timed invocation to realize the property of least suffering. One is synchronous timed invocation, and the other is asynchronous timed invocation. ffl To realize the property of best effort, it introduces a new notion, called timing polymorphism, which allows the ....
Ishikawa, Y., Tokuda, H. and Mercer, C. W., Object-Oriented Real-Time Language Design: Constructs for Timing Constraints, Proceedings of ECOOP/OOPSLA'90, October, p289-298, 1990.
.... of integration have existed for some time, but do not span the software development cycle [1] In most system, functional abstraction is supported by some off theshelf design language followed by implementation with a real time programming language such as Spring C [14, 16] extensions to C [12, 19, 13], extensions to the PEARL process control language [23] or others [3, 8] This paper discusses SDL, which provides a simple but comprehensive way to collect, use, modify, and exchange descriptive information at the level of detail required to write, translate, analyze, and predictably execute ....
Ishikawa, Y., Tokuda, H., and Mercer, C. Object Oriented Real-Time Language Design: Constructs for Timing Constraints. In Proceedings of OOPSLA /ECOOP. ACM, October 1990.
.... language with temporal extensions that has some similarities to the translation described here, but does not address how the behavior of the program can be accurately predicted, and then reliably produced by the underlying system [12] This is also true of the object oriented language described in [3]. The WCET is an important aspect of real time process behavior, though it is by no means the only aspect of behavior that must be predicted. At the simplest level, any method of calculating WCET for the code of a process, or a section of it, will require summation of the execution times for ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object Oriented Real-Time Language Design: Constructs for Timing Constraints. In Proceedings of OOPSLA/ECOOP. ACM, October 1990.
....however, try to ease the task of estimating the number of general loop iterations by forbidding general loops, i.e. by forcing the user to supply constant upper bounds for the number of iterations. Another approach is to let the user specify a time bound within the loop has to complete (cf. e.g. [ITM90]) In any case the user, i.e. the programmer, has to react to such exceptional cases. In this paper we will narrow the gap between general loops and for loops by defining discrete loops. These loops are known to complete and are easy to analyze (especially their number of iterations) and capture ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object-oriented real-time language design: Constructs for timing constraints. In ECOOP/OOPSLA '90 Proceedings, pages 289--298, October 1990.
....try to ease the task of estimating the number of general loop iterations by forbidding general loops, i.e. by forcing the user to supply constant upper bounds for the number of iterations. Another approach is to let the user specify a time bound within the loop has to complete (cf. e.g. [12]) In any case the user, i.e. the programmer, has to react to such exceptional cases. In this paper we will follow a different approach: We will narrow the gap between general loops and for loops by defining discrete loops. These loops are known to complete and are easy to analyze (especially ....
Y. Ishikawa, H. Tokuda, and C. W. Mercer. Object-oriented real-time language design: Constructs for timing constraints. In ECOOP/OOPSLA '90 Proceedings, pages 289--298, October 1990.
....comparison to these latter two languages and a couple of recent proposals that were not considered in the mentioned surveys. In the next couple of subsections we briefly describe the features with regard to timing of Ada [1, 4] RT Euclid [16] and the object oriented languages DROL [23] RTC [15], FLEX [20] and Sina (with real time extensions) 3, 5] After that we discuss the major differences with our approach. 14 COMPARISON WITH OTHER APPROACHES 38 14.1 ADA The Ada language [4] was developed to supply the US Department of Defense with a programming language for embedded applications. ....
....flexible with regard to synchronization and exception handling. However, the best effort approach can not result in guarantees on timing behavior. Composability and abstraction of timing behavior of DRObjects is not explicitly addressed. 14 COMPARISON WITH OTHER APPROACHES 41 14.4 RTC RTC [15] is also implemented on the ARTS kernel. The ARTS RTC platform is an environment for the development of distributed object oriented real time systems. It differs form the DROL language in that it focuses almost exclusively on the issues that are directly addressed by the kernel. It has a lesser ....
Y. Ishikawa, H. Tokuda, and C.W. Mercer, "Object-Oriented Real-Time Language Design: Constructs for Timing Constraints", Carnegie Mellon, 1990.
No context found.
Y. Ishikawa, H. Tokuda, and C. Mercer. Object-Oriented Real-Time Language Design: Constructs for Timing Constraints. In Proceedings of the ACM Object-Oriented Programming: Systems, Languages and Applications, pages 289--296, October 1990.
No context found.
Y. Ishikawa, H. Tokuda, and C. W. Mercer, "Object-oriented real-time language design: Constructs for timing constraints," ACM SIGPLAN Notices, ECOOP/OOPSLA'90 Proceedings, Vol. 25, pp. 289--298, October 1990.
No context found.
Y. Ishikawa, et al., "Object Oriented Real-Time Language Design: Constructs for Timing Constraints", ECOOP/OOPSLA 90 Proceedings, October 1990, pp. 289-298.
No context found.
ISHIKAWA, Y., TOKUDA, H., AND MERCER, C. W. 1990. Object-oriented real-time language design: Constructs for timing constraints. In Proceedings of the OOPSLA/ECOOP '90 Conference on Object-Oriented Programming Systems, Languages and Applications. ACM SIGPLAN Not. 25, 10, 289--298.
No context found.
ITM90. Yutaka Ishikawa, Hideyuki Tokuda, and Clifford W. Mercer, Object-oriented real-time language design: Constructs for timing constraints, ECOOP/OOPSLA '90 Proceedings, October 1990, pp. 289--298.
No context found.
Yutaka Ishikawa, Hideyuki Tokuda, and Clifford W. Mercer. Object-oriented real-time language design: Constructs for timing constraints. In ECOOP/OOPSLA '90 Proceedings, pages 289--
First 50 documents Next 50
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