9 citations found. Retrieving documents...
Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Towards Device Driver Synthesis - Lehmann (2002)   (Correct)

....and is directly integrated in the target code (see low level access functions under Linux [95] In this chapter, the application of known compiler techniques in the special field of device driver programming is briefly discussed. As reference for compiler techniques, mainly [66] and additionally [54, 68, 81, 120, 32] have been used. 8.1.1 Techniques and Pre conditions State of the art compiler techniques are code hoisting, constant folding, control flow analysis, dead code elimination, and code re ordering, just to name a few. The main question is, which optimisations can safely be done in combination with ....

Thomas W. Parsons. An Introduction to Compiler Construction. W.H. Freeman and Company, 1997.


Regular Expressions - a Graphical User Interface - Kahrs (1999)   (Correct)

....and then applies the rules step by step until no further re nements are possible bottom up; here, rst the atomic components of the regular expression are translated into NFAs the rules say how these NFAs are then combined. 2 The most commonly used form in the literature is bottom up [ASU86, TS85, Mar91, Par92], but top down has some supporters as well [WM95, PP92] For hand drawing purposes, the bottom up strategy is best, for two reasons: rst, it does not require the erasure of earlier drawn bits; second, the graphs grow outwards which means that one usually avoids overcrowding problems in the ....

....# # ######## x ## # # # # # # # # # ## # # # # # # # # # ######## y ######## c s ## ######## d ## # # # # # # # # # This is very safe as it is correct and safe without any safety requirements for r and s . This is the most commonly used rule in the literature [ASU86, TS85, PP92, Lou97, Par92, Mor98, HU79]. 3 Quite frankly, this is mad. Unsurprisingly, they optimise quite a few s away when they demonstrate the translation at an example. 5 The price paid for this amount of safety are four extra states and four extra transitions. Bernstein and Sippu Soisalon Soininen translate two of these ....

[Article contains additional citation context not shown here]

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, 1992.


javab Manual (version 1.0BETA) - Bik, Gannon   (Correct)

.... p option. 3 Automatic Loop Parallelization of JVM Bytecode If the p flag is given, javab examines the JVM bytecode of every method in each class file to automatically detect and exploit implicit parallelism in the natural loops that are defined by back edges in the flow graph (see e.g. [1, 2, 10, 21, 24, 25]) The default approach taken by javab to preserve the user visible state after exceptions [16] as much as possible (without being over restrictive with respect to transformations) is to only transform regions of code for which the compiler can prove that run time exceptions cannot occur, but to ....

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.


Automatically Exploiting Implicit Parallelism in Java - Bik, Gannon   (18 citations)  (Correct)

.... for (int i = low; i high; i ) body(i) Furthermore, we assume that the compiler has ascertained that loop Li can be executed in either a DOALL or DOACROSS like manner, possibly after standard compiler optimizations, loop normalization, and possibly other loop transformations (see e.g. [1, 10, 28, 29, 35, 36, 37] are used to enhance the opportunities of loop parallelization. The parallelization itself proceeds as follows, where, for simplicity, new identifiers that may conflict with other identifiers are denoted with a suffix x . In reality, however, an appropriate suffix must be generated by the ....

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.


A Strategy for Exploiting Implicit Loop Parallelism in Java.. - Bik, Gannon (1996)   (1 citation)  (Correct)

.... In this paper, we focus on the parallelization of stride 1 loops that have the following form: L1: for (int i = low; i high; i ) body(i) Note that conventional compiler techniques, like constant propagation, scalar forward substitution, induction variable substitution, and loop normalization [1, 11, 24, 29] may be useful to convert some other loop constructs into this form. In essence, the parallelization of the a loop merely consists of adding a new method runL1 to the class in which this loop occurs: void runL1(int l, int h, int s) for (int i = l; i h; i = s) body(i) If the loop occurs in ....

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.


javar - a prototype Java restructuring compiler - Bik, Gannon (1997)   (14 citations)  (Correct)

.... for (int i = low; i high; i ) body(i) Furthermore, we assume that the compiler has ascertained that loop Li can be executed in either a DOALL or DOACROSS like manner, possibly after standard compiler optimizations, loop normalization, and possibly other loop transformations (see e.g. [1, 11, 32, 33, 39, 40, 41] are used to enhance the opportunities of loop parallelization. The parallelization itself proceeds as follows, where, for simplicity, new identifiers that may conflict with other identifiers are denoted with a suffix x . In reality, however, an appropriate suffix must be generated by the ....

.... 0) i j) i ; while ( a[j] BIT[b] 0) i j) j ; t = a[i] a[i] a[j] a[j] t; while (j = i) if ( a[r] BIT[b] 0) j ; radixsort(a,l,j 1,b 1) radixsort(a,j,r, b 1) The static initializer show below can be used to initialize array BIT: static int [ BIT = new int[32]; static int k = 1; for (int i = 0; i 32; i ) BIT[i] k; k = 2; An array of positive 32 bit integers (with a zero most significant bit) for example, can be sorted by calling radixsort( with b = 30. Because the two recursive method invocations can be done in parallel, radixsort( is ....

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.


The FeedBack Compiler - Binkley, Duncan, Jubb, Wielgosz   (Correct)

....For consistency, a video taped lecture was used. Following the lecture, a ten minute pre test was given to get a baseline measure of the students comprehension of cse. The final part of the shared component was 25 minutes of reading written material on cse adapted from several compiler texts [1, 14, 18, 21, 20, 24]. After the shared component, the control and experimental groups were split to perform the experiential component. The control group continued to read the written materials and work on the exercises for an additional thirty minutes. The experimental group was taken to a computer lab and performed ....

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, New York, 1992.


Automatically Exploiting Implicit Parallelism in Java - Aart Bik And   (Correct)

No context found.

Thomas W. Parsons. Introduction to Compiler Construction. Computer Science Press, New York, 1992.


Design and Implementation of a Probabilistic Word Prediciton.. - Carlberger (1997)   (3 citations)  (Correct)

No context found.

Parsons, T. W. (1992) Introduction to Compiler Construction, Computer Science Press.

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