<?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-07-26T16:44:46Z</responseDate>
  <request identifier="3114" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:3114</identifier>
        <datestamp>2024-03-06T10:33:51Z</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>Modular Termination Proofs of Recursive Java Bytecode Programs by Term Rewriting</dc:title>
          <dc:creator>Brockschmidt, Marc</dc:creator>
          <dc:creator>Otto, Carsten</dc:creator>
          <dc:creator>Giesl, Jürgen</dc:creator>
          <dc:subject>termination</dc:subject>
          <dc:subject>Java Bytecode</dc:subject>
          <dc:subject>term rewriting</dc:subject>
          <dc:subject>recursion</dc:subject>
          <dc:description>In earlier work we presented an approach to prove termination of &#13;
non-recursive Java Bytecode (JBC) programs automatically. Here, &#13;
JBC programs are first transformed to finite termination graphs&#13;
which represent all possible runs of the program.&#13;
Afterwards, the termination graphs are translated to term&#13;
rewrite systems (TRSs) such that termination of the resulting TRSs&#13;
implies termination of the original JBC programs. So in this way,&#13;
existing techniques and tools from term rewriting can be used to &#13;
prove termination of JBC automatically. In this paper, we improve&#13;
this approach substantially in two ways:&#13;
&#13;
(1) We extend it in order to also analyze recursive JBC programs. &#13;
    To this end, one has to represent call stacks of arbitrary&#13;
    size.&#13;
&#13;
(2) To handle JBC programs with several methods, we modularize our&#13;
    approach in order to re-use termination graphs and TRSs for the &#13;
    separate methods and to prove termination of the resulting TRS &#13;
    in a modular way.&#13;
&#13;
We implemented our approach in the tool AProVE. Our experiments show &#13;
that the new contributions increase the power of termination analysis &#13;
for JBC significantly.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Marc Brockschmidt and Carsten Otto and Jürgen Giesl</dc:contributor>
          <dc:date>2011</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 10, 22nd International Conference on Rewriting Techniques and Applications (RTA'11) (2011)</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.RTA.2011.155</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-31146</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.RTA.2011.155</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by-nc-nd/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
