Coverage-driven Automated Compiler Test Suite Generation

Kalinov, Alexey; Kossatchev, A. S.; Petrenko, Alexander K.; Posypkin, Mikhail; Shishkov, Vladimir

doi:10.1016/s1571-0661(05)82625-8

Cited by 10 publications

(7 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To implement this approach, statements for printing values of variables [12,19,[21][22][23] or expressions [9] are inserted into the test program used for testing the compiler. For the evaluation of reference results, an attribute grammar [21], or a partial specification of the dynamic semantics [9], or a different implementation of the compiler [12] are used.…”

Section: Test Oracles For the Optimizing Transformation And Code Genementioning

confidence: 99%

“…For the evaluation of reference results, an attribute grammar [21], or a partial specification of the dynamic semantics [9], or a different implementation of the compiler [12] are used. In [19,22,23], to obtain the reference observable behavior, an interpreter of the dynamic semantics is used. Usually, a simplified model, in which the program has no input data, is considered.…”

Section: Test Oracles For the Optimizing Transformation And Code Genementioning

confidence: 99%

See 1 more Smart Citation

Survey of compiler testing methods

Kossatchev

Posypkin

2005

Program Comput Soft

View full text Add to dashboard Cite

Compilers are used for creating executable modules for programs written in high-level languages; therefore, the presence of errors in a compiler is a serious danger for the quality of the software developed with the use of this compiler. As in the case of any other software, testing is one of the most important methods of quality control and error detection in compilers. The survey is devoted to methods for generating, running, and checking the quality of compiler test suites, which are based on formal specifications of the programming language syntax and semantics.

show abstract

Section: Test Oracles For the Optimizing Transformation And Code Genementioning

confidence: 99%

Section: Test Oracles For the Optimizing Transformation And Code Genementioning

confidence: 99%

Survey of compiler testing methods

Kossatchev

Posypkin

2005

Program Comput Soft

View full text Add to dashboard Cite

show abstract

“…Methods of automated test generation and coverage criteria for negative tests for the language semantics by its formal description are suggested in [19]. In this paper, the so-called constraint coverage criterion is proposed, which is based on the analysis of the causes of violation of the context condition.…”

Section: Testing Of the Static Semantics Analysis Stagementioning

confidence: 99%

“…In [19], the Montages formalism was used for specifying and generating tests for a compiler from the mpC parallel programming language [31]. The authors suggest a number of coverage criteria for the Montages specifications and, in particular, coverage criteria for the dynamic semantics.…”

Section: Tests For Checking Dynamic Semanticsmentioning

confidence: 99%

Survey of Compiler Testing Methods

Kossatchev

Posypkin

2005

Program Comput Soft

View full text Add to dashboard Cite

show abstract

“…We remark that these two oracles are 'weak' as they are unable to detect simple semantic errors such as 3 + 4 = 8. The third, stronger oracle is one that checks whether the output of a test program is consistent with a reference, which could be a second compiler (i.e., differential testing [45]), or an abstract specification like a state machine [35,36]. This oracle requires a reference, which is not always feasible.…”

Section: Introductionmentioning

confidence: 99%

SpecTest: Specification-Based Compiler Testing

Schumi

Sun

2021

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Compilers are error-prone due to their high complexity. They are relevant for not only general purpose programming languages, but also for many domain specific languages. Bugs in compilers can potentially render all programs at risk. It is thus crucial that compilers are systematically tested, if not verified. Recently, a number of efforts have been made to formalise and standardise programming language semantics, which can be applied to verify the correctness of the respective compilers. In this work, we present a novel specification-based testing method named SpecTest to better utilise these semantics for testing. By applying an executable semantics as test oracle, SpecTest can discover deep semantic errors in compilers. Compared to existing approaches, SpecTest is built upon a novel test coverage criterion called semantic coverage which brings together mutation testing and fuzzing to specifically target less tested language features. We apply SpecTest to systematically test two compilers, i.e., the Java compiler and the Solidity compiler. SpecTest improves the semantic coverage of both compilers considerably and reveals multiple previously unknown bugs.

show abstract

Coverage-driven Automated Compiler Test Suite Generation

Cited by 10 publications

References 7 publications

Survey of compiler testing methods

Survey of compiler testing methods

Survey of Compiler Testing Methods

SpecTest: Specification-Based Compiler Testing

Contact Info

Product

Resources

About