Well-typed programs can go wrong: A study of typing-related bugs in JVM compilers

Stefanos Chaliasos, Thodoris Sotiropoulos, Georgios Petros Drosos, Charalambos Mitropoulos, Dimitris Mitropoulos, Diomidis Spinellis

Research output: Contribution to journalArticleScientificpeer-review

15 Downloads (Pure)

Abstract

Despite the substantial progress in compiler testing, research endeavors have mainly focused on detecting compiler crashes and subtle miscompilations caused by bugs in the implementation of compiler optimizations. Surprisingly, this growing body of work neglects other compiler components, most notably the front-end. In statically-typed programming languages with rich and expressive type systems and modern features, such as type inference or a mix of object-oriented with functional programming features, the process of static typing in compiler front-ends is complicated by a high-density of bugs. Such bugs can lead to the acceptance of incorrect programs (breaking code portability or the type system's soundness), the rejection of correct (e.g. well-typed) programs, and the reporting of misleading errors and warnings. We conduct, what is to the best of our knowledge, the first empirical study for understanding and characterizing typing-related compiler bugs. To do so, we manually study 320 typing-related bugs (along with their fixes and test cases) that are randomly sampled from four mainstream JVM languages, namely Java, Scala, Kotlin, and Groovy. We evaluate each bug in terms of several aspects, including their symptom, root cause, bug fix's size, and the characteristics of the bug-revealing test cases. Some representative observations indicate that: (1) more than half of the typing-related bugs manifest as unexpected compile-time errors: the buggy compiler wrongly rejects semantically correct programs, (2) the majority of typing-related bugs lie in the implementations of the underlying type systems and in other core components related to operations on types, (3) parametric polymorphism is the most pervasive feature in the corresponding test cases, (4) one third of typing-related bugs are triggered by non-compilable programs. We believe that our study opens up a new research direction by driving future researchers to build appropriate methods and techniques for a more holistic testing of compilers.

Original languageEnglish
Article number123
Number of pages30
JournalProceedings of the ACM on Programming Languages
Volume5
Issue numberOOPSLA
DOIs
Publication statusPublished - 2021

Keywords

  • compiler bugs
  • compiler testing
  • Groovy
  • Java
  • Kotlin
  • Scala
  • static typing

Fingerprint

Dive into the research topics of 'Well-typed programs can go wrong: A study of typing-related bugs in JVM compilers'. Together they form a unique fingerprint.

Cite this