<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-09-29T22:40:18Z</responseDate>
  <request identifier="6116" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:6116</identifier>
        <datestamp>2026-09-22T21:59:22Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Boomerang: Demand-Driven Flow- and Context-Sensitive Pointer Analysis for Java</dc:title>
          <dc:creator>Späth, Johannes</dc:creator>
          <dc:creator>Nguyen Quang Do, Lisa</dc:creator>
          <dc:creator>Ali, Karim</dc:creator>
          <dc:creator>Bodden, Eric</dc:creator>
          <dc:subject>Demand-Driven; Static Analysis; IFDS; Aliasing; Points-to Analysis</dc:subject>
          <dc:description>Many current program analyses require highly precise pointer&#13;
information about small, tar- geted parts of a given program. This&#13;
motivates the need for demand-driven pointer analyses that compute&#13;
information only where required. Pointer analyses generally compute&#13;
points-to sets of program variables or answer boolean alias&#13;
queries. However, many client analyses require richer pointer&#13;
information. For example, taint and typestate analyses often need to&#13;
know the set of all aliases of a given variable under a certain&#13;
calling context. With most current pointer analyses, clients must&#13;
compute such information through repeated points-to or alias queries, increasing complexity and computation time for them.&#13;
&#13;
This paper presents Boomerang, a demand-driven, flow-, field-, and&#13;
context-sensitive pointer analysis for Java programs. Boomerang&#13;
computes rich results that include both the possible allocation sites of a given pointer (points-to information) and all pointers that can point to those allocation sites (alias information). For increased precision and scalability, clients can query Boomerang with respect to particular calling contexts of interest.&#13;
&#13;
Our experiments show that Boomerang is more precise than existing&#13;
demand-driven pointer analyses. Additionally, using Boomerang, the&#13;
taint analysis FlowDroid issues up to 29.4x fewer pointer queries&#13;
compared to using other pointer analyses that return simpler pointer&#13;
infor- mation. Furthermore, the search space of Boomerang can be&#13;
significantly reduced by requesting calling contexts from the client&#13;
analysis.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Johannes Späth and Lisa Nguyen Quang Do and Karim Ali and Eric Bodden</dc:contributor>
          <dc:date>2016</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 56, 30th European Conference on Object-Oriented Programming (ECOOP 2016)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ECOOP.2016.22</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-61164</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ECOOP.2016.22</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
