skip to main content
article
Open Access

Automatic isolation of compiler errors

Published:01 September 1994Publication History
Skip Abstract Section

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. BENITEZ, M. E. AND DAVIDSON, J.W. 1955. A portaDle gloDal optimizer ano nnKer. ~i~ r:-uce~u:- ings of the SIGPLAN "88 Symposium on Programming Language Design and Implementation (June). ACM, New York, 329-338. Google ScholarGoogle Scholar
  2. BOYD, M. Z. AND WHALLEY, D. B. 1992. isolation and analysis of optimization errors. In Proceedings of the SIGPLAN '93 Conference on Programming Language Design and Implementation (June). ACM, New York, 26-35. Google ScholarGoogle Scholar
  3. CARON, J. M. AND DARNELL, P.A. 1990. Bugiind" a tool for debugging optimizing compilers. In SIGPLAN Not. 25, 1 (Jan.), 17-22. Google ScholarGoogle Scholar
  4. DAVIDSON, J. AND HOLLER, A. 1988. A Study of a C function inliner. Softw. Prac. Exper. 18, 8 (Aug.), 775-790. Google ScholarGoogle Scholar
  5. DAVIDSON, J. AND WHALLEY, D.B. 1991. A designenvironment for addressing architecture and compiler interactions. In Microprocess. Microsyst. 15, 9 (Nov.), 459-472.Google ScholarGoogle Scholar
  6. DAVIDSON, J. W. AND WHALLEY, D. B. 1989. Quick compilers using peephole optimizations. Softw. Prac. Exper. 19, 1 (Jun.), 195-203. Google ScholarGoogle Scholar
  7. HENNESSY, J. AND PATTERSON, D. 1990. Computer Architecture: A Quantitative Approach, Morgan Kaufmann, San Mateo, Calif. Google ScholarGoogle Scholar
  8. JOHNSON, S.C. 1979. A tour through the portable C compiler. In Unix Programmer's Manual, 7th Edition 2B. Section 33 (Jan.).Google ScholarGoogle Scholar
  9. MUELLER, F. AND WHALLEY, D.B. 1992. Avoiding unconditional jumps by code replication. In Proceedings of the SIGPLAN "92 Conference on Programming Language Design and implementation (June). ACM, New York, 322-330. Google ScholarGoogle Scholar
  10. WULF, W., JOHNSSON, R. K., WEINSTOCK, C. B., HOBBS, S. O., AND GESCHKE, C.M. 1975. The Design of an Optimizing Compiler. American Elsevier, New York. Google ScholarGoogle Scholar

Index Terms

  1. Automatic isolation of compiler errors

      Recommendations

      Comments

      Login options

      Check if you have access through your login credentials or your institution to get full access on this article.

      Sign in

      Full Access

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader