CIL: Intermediate Language and Tools for Analysis and Transformation of C Programs

By George C. Necula, Scott McPeak, Shree Prakash Rahul, Westley Weimer. International Conference on Compiler Construction, 2002

1,152 citations recorded by the source corpus.

Subfields: Artificial Intelligence, Software, Signal Processing

View Paper: https://www.semanticscholar.org/paper/585706dc56e146c8fb42228fc5cbe1de0bb0a69d

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Software

In Signal Processing

Citations in the corpus

Software Verification with BLAST (2003, methodology): “Our tool is written in Objective Caml, and uses the CIL compiler infrastructure [7] as a front end to parse C programs.”
Symbolic Robustness Analysis (2009, methodology): “Splat uses CIL [14] for internal representation of a C program.”
Simulating the power consumption of large-scale sensor network applications (2004, methodology): “This is accomplished using C Intermediate Language (CIL) [16], a toolkit for programmatically manipulating C source code .les.”
DART: directed automated random testing (2005, methodology): “In our implementation of DART for C, the code instrumentation needed to intertwine the concrete execution of the program P with the symbolic calculations performed by DART as described in function instrumented program() (see Section 2) is performed using CIL [28], an OCAML application for parsing”
A Formally Verified Compiler Back-end (2009, methodology): “This parser is built on top of the CIL library [77].”
Bringing the web up to speed with WebAssembly (2017, methodology): “Our work was directly informed by experience with stack machines such as the JVM [27] and CIL [33] and their validation algorithms.”
A Software Analysis Perspective (2012, methodology): “Frama-C is based on CIL [43], a front-end for C that parses ISO C99 programs into their normalized representation: loop constructs are given a single form, expressions have no sideeffects, etc.”
CUTE: a concolic unit testing engine for C (2005, methodology): “For example, CIL converts **v”
CCured: type-safe retrofitting of legacy software (2005, methodology): “2 Any solution to the set of constraints C assigns a pointer kind to every quali.er 2For simplicity, we assume that all such casts are made explicit; in fact, the CIL [Necula et al. 2002b] infrastructure that we use to implement CCured will add such casts automatically.”
The software model checker Blast (2007, background): “Any C program can be converted to this representation [70].”