Static Worst-Case Execution Time (WCET) analysis is a technique to derive upper bounds for the execution times of programs. Such bounds are crucial when designing and verifying real-time systems. A key component for statically deriving safe and tight WCET bounds is information on the possible program flow through the program. Such flow information can be provided manually by user annotations, or automatically by a flow analysis. To make WCET analysis as simple and safe as possible, it should preferably be automatically derived, with no or very limited user interaction.In this paper we present a method for deriving such flow information called abstract execution. This method can automatically calculate loop bounds, bounds for including nested loops, as well as many types of infeasible paths. Our evaluations show that it can calculate WCET estimates automatically, without any user annotations, for a range of benchmark programs, and that our techniques for nested loops and infeasible paths sometimes can give substantially better WCET estimates than using loop bounds analysis only.

Published in Petroleum Transactions, AIME, Volume 213, 1958, pages 36–43. Abstract The effect of fluid-flow rate and fluid viscosity on oil-water relative permeability determinations was studied using the "dynamic flow technique." In this work relative permeability curves were obtained for homogeneous small core samples from several sandstone outcrop formations. Radio-tracers were used for the determination of fluid saturation and for the detection of saturation gradients. Cobalt–60 in the form of cobaltous chloride was used as a water-phase tracer in some of the experiments. Iodine–131 in the form of iodobenzene and Mercury–203 in the form of mercury diphenyl were used as oil-phase tracers in other experiments. Flow rates for each phase were varied within a range of 2.5 to 140.6 ml/hr. Oil-phase viscosities under flowing conditions were varied from 0.398 to 1.683 cp. The relative permeabilities obtained were found to be solely a function of saturation and independent of flow rate, provided there was no saturation gradient induced in the core sample by "boundary effect." Even though equilibrium with respect to flowing conditions was obtained at the lower flow rates, where a saturation gradient exists, this equilibrium is of a "contingent" -type rather than the "steady-state" equilibrium implicit in the relative permeability concept. The only effect of increasing the oil or non-wetting phase viscosity was to decrease the flow rate required for the elimination of the boundary effect. Fairly good agreement between experimentally determined and calculated values of the boundary effect was obtained when the non-wetting oil phase was the only flowing phase. Introduction In the characterization of reservoir rock, as well as in the solution of reservoir production problems, it is most desirable to have reliable relative permeability measurements for the rock and fluids of interest. Many techniques have been developed for the laboratory determination of the relative permeability of both large and small core samples. In varying degree, difficulties attend the use of all of the methods. Each of the methods requires the metered flow of fluids of known viscosity through the core sample under conditions wherein the pressure drop in the individual flowing phases can be measured or closely approximated. Since the relative permeability is a function of the saturation and distribution of the flowing fluids, some means of obtaining such information is also required.

No abstract

Abstract

A static Worst-Case Execution Time (WCET) analysis derives upper bounds for the execution times of programs. Such analysis requires information about the possible program flows. The current practice is to provide this information manually, which can be laborious and error-prone. An alternative is to derive this information through an automated flow analysis.In this article, we present a case study where an automatic flow analysis method was tested on industrial real-time system code. The same code was the subject of an earlier WCET case study, where it was analysed using manual annotations for the flow information. The purpose of the current study was to see to which extent the same flow information could be found automatically. The results show that for the most part this is indeed possible, and we could derive comparable WCET estimates using the automatically generated flow information. In addition, valuable insights were gained on what is needed to make flow analysis methods work on real production code.