Automatic isolation of compiler errors

ABSTRACT

This paper describes a tool called vpoiso that was developed to isolate errors automatically in the vpo compiler system. The two general types of compiler errors isolated by this tool are optimization and nonoptimization errors. When isolating optimization errors, vpoiso relies on the vpo optimizer to identify sequences of changes, referred to as transformations, that result in semantically equivalent code and to provide the ability to stop performing improving (or unnecessary) transformations after a specified number have been performed. A compilation of a typical program by vpo often results in thousands of improving transformations being performed. The vpoiso tool can automatically isolate the first improving transformation that causes incorrect output of the execution of the compiled programs by using a binary search that varies the number of improving transformation performed. Not only is the illegal transformation automatically isolated, but vpoiso also identifies the location and instant the transformation is performed in vpo. Nonoptimization errors occur from problems in the front end, code generator, and necessary transformations in the optimizer. If another compiler is available that can produce correct (but perhaps more inefficient) code, then vpoiso can isolate nonoptimization errors to a single function. Automatic isolation of compiler errors facilitates retargeting a compiler to a new machine, maintenance of the compiler, and supporting experimentation with new optimizations.

REFERENCES

• 1: M. E. Benitez , J. W. Davidson, A portable global optimizer and linker, Proceedings of the ACM SIGPLAN 1988 conference on Programming Language design and Implementation, p.329-338, June 20-24, 1988, Atlanta, Georgia, United States
• 2: Mickey R. Boyd , David B. Whalley, Isolation and analysis of optimization errors, Proceedings of the ACM SIGPLAN 1993 conference on Programming language design and implementation, p.26-35, June 21-25, 1993, Albuquerque, New Mexico, United States
• 3: J. M. Caron , P. A. Darnell, Bugfind: a tool for debugging optimizing compilers, ACM SIGPLAN Notices, v.25 n.1, p.17-22, Jan. 1990 [doi>10.1145/74105.74106]
• 4: Jack W. Davidson , Anne M. Holler, A study of a C function inliner, Software—Practice & Experience, v.18 n.8, p.775-790, August 1988 [doi>10.1002/spe.4380180805]
• 5: DAVIDSON, J. AND WHALLEY, D.B. 1991. A designenvironment for addressing architecture and compiler interactions. In Microprocess. Microsyst. 15, 9 (Nov.), 459-472.
• 6: Jack W. Davidson , David B. Whalley, Quick compilers using peephole optimization, Software—Practice & Experience, v.19 n.1, p.79-97, Jan. 1989 [doi>10.1002/spe.4380190108]
• 7: David A. Patterson , John L. Hennessy, Computer architecture: a quantitative approach, Morgan Kaufmann Publishers Inc., San Francisco, CA, 1990
• 8: JOHNSON, S.C. 1979. A tour through the portable C compiler. In Unix Programmer's Manual, 7th Edition 2B. Section 33 (Jan.).
• 9: Frank Mueller , David B. Whalley, Avoiding unconditional jumps by code replication, Proceedings of the ACM SIGPLAN 1992 conference on Programming language design and implementation, p.322-330, June 15-19, 1992, San Francisco, California, United States
• 10: William Allan Wulf , Richard K. Johnsson , Charles B. Weinstock , Steven O. Hobbs , Charles M. Geschke, The Design of an Optimizing Compiler, Elsevier Science Inc., New York, NY, 1975

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.5 Testing and Debugging
          Subjects: Debugging aids

Additional Classification:
  D. Software
  D.3 PROGRAMMING LANGUAGES
      D.3.4 Processors
          Subjects: Optimization; Compilers

General Terms:
Algorithms, Languages

Keywords:
automatic error isolation, diagnosis procedures, nonoptimization errors, optimization errors