Commit-time Incremental Analysis
Most changes to large systems that have been deployed are quite small compared to the size of the entire system. While standard summary-based analyses reduce the code that is reanalysed, they, nevertheless, analyse code that is not changed. For example, a backward summary-based analysis, will examine all the callers of the changed code even if the callers themselves have not changed. In this paper we present a novel approach of having summaries of the callers (called forward summaries) that enables one to analyse only the changed code. An evaluation of this approach on two representative examples, demonstrates that the overheads associated with the generation of the forward summaries is recovered by performing just one or two incremental analyses. Thus this technique can be used at commit-time where only the changed code is available.
Sat 22 JunDisplayed time zone: Tijuana, Baja California change
09:15 - 11:00 | Performance and Optimizations for Program Analysis ToolsSOAP at 106A Chair(s): Neville Grech University of Athens | ||
09:15 20mTalk | Commit-time Incremental Analysis SOAP | ||
09:35 20mTalk | Know Your Analysis: How Instrumentation Aids Understanding Static Analysis SOAP Philipp Dominik Schubert Heinz Nixdorf Institut, Paderborn University, Richard Leer Heinz Nixdorf Institut, Paderborn University, Ben Hermann Paderborn University, Eric Bodden Heinz Nixdorf Institut, Paderborn University and Fraunhofer IEM Pre-print Media Attached | ||
09:55 20mTalk | Fixpoint Reuse for Incremental JavaScript Analysis SOAP Lawton Nichols , Mehmet Emre University of California, Santa Barbara, Ben Hardekopf UC Santa Barbara | ||
10:15 80mTalk | Program Analysis for Process Migration SOAP | ||
10:35 25mOther | Open Discussion on Previous Talks 1 SOAP |