Re: value range tracing

David Whalley <whalley@sed.cs.fsu.edu>
9 Dec 1995 19:01:20 -0500

          From comp.compilers
Related articles
Value range tracing jeremy@suede.sw.oz.au (1995-12-01)
Re: value range tracing whalley@sed.cs.fsu.edu (David Whalley) (1995-12-09)
Re: Value range tracing hbaker@netcom.com (1995-12-09)
Re: Value range tracing preston@tera.com (1995-12-09)
Re: Value range tracing schinz@guano.alphanet.ch (1995-12-09)
Value range tracing dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-12-09)
Re: Value range tracing bernecky@eecg.toronto.edu (1995-12-09)
Re: Value range tracing creusil@cri.ensmp.fr (1995-12-09)
[6 later articles]
| List of all articles for this month |
From: David Whalley <whalley@sed.cs.fsu.edu>
Newsgroups: comp.compilers
Date: 9 Dec 1995 19:01:20 -0500
Organization: Compilers Central
References: 95-12-014
Keywords: analysis, optimize, bibliography

>I'm wondering if people bother with value range tracing. That is,
>keeping track of the possible range of variables at each point in the
>program.


Look at the following two papers in PLD&I '95.


%T Avoiding Conditional Branches by Code Replication
%A F. Mueller
%A D. B. Whalley
%J Proceedings of the SIGPLAN '95 Conference on Programming Language Design and Implementation
%C La Jolla, CA
%D June 1995
%P 56-66


%T Accurate Static Branch Prediction by Value Range Propagation
%A J. Patterson
%J Proceedings of the SIGPLAN '95 Conference on Programming Language Design and Implementation
%C La Jolla, CA
%D June 1995
%P 67-78


The first paper described a technique to avoid branches by code replication.
One technique used was to determine when one conditional branch result would
subsume another branch.


The second paper was about a method that performed better branch prediction
by tracking the ranges of variables.


Dave Whalley
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.