<?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-21T12:31:37Z</responseDate>
  <request identifier="1569" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:1569</identifier>
        <datestamp>2024-03-06T11:08:06Z</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>Source-To-Source Analysis with SATIrE - an Example Revisited</dc:title>
          <dc:creator>Schordan, Markus</dc:creator>
          <dc:subject>Source-to-source analysis</dc:subject>
          <dc:subject>ARAL</dc:subject>
          <dc:subject>Annotation Language</dc:subject>
          <dc:description>Source-to-source analysis aims at supporting the reuse of analysis results&#13;
similar to code reuse. The reuse of program code is a common&#13;
technique which attempts to save time and costs by reducing redundant&#13;
work. We want to avoid re-analyzing parts of a software system, such&#13;
as library code. In the ideal case the analysis results are directly&#13;
associated with the program itself. Source-to-source analysis supports&#13;
this through program annotations. Further more, to get the best out of&#13;
available software analysis tools, we aim at enabling the&#13;
combination of the analysis results of different tools. In order to&#13;
allow this, tools must be able to process another tool's analysis&#13;
results. This enables numerous applications such as automatic&#13;
annotation of interfaces, testing of analyses by checking the results&#13;
of an analysis against provided annotations, domain aware analysis by&#13;
utilizing domain-specific program annotations, and making analysis&#13;
results persistent as annotations in source code.&#13;
&#13;
The design of the {em Static Analysis Tool Integration Engine}&#13;
(SATIrE cite{satirewebsite}) allows to map source code annotations to&#13;
its intermediate program representation as well as generating source&#13;
code annotations from analysis results that are attached to the&#13;
intermediate representation. The technical challenges are the design&#13;
of the analysis information annotation language, the bidirectional&#13;
propagation of the analysis information through different phases of&#13;
the internal translation processes, and the combination of the&#13;
different analyses through the plug-in mechanism. In its current&#13;
version SATIrE targets C/C++ programs. In this paper we present the&#13;
approach of source-to-source analysis and show in a detailed example&#13;
analysis how we support this approach in SATIrE.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Markus Schordan</dc:contributor>
          <dc:date>2008</dc:date>
          <dc:relation>Is Part Of Dagstuhl Seminar Proceedings, Volume 8161, Scalable Program Analysis (2008)</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/DagSemProc.08161.7</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-15693</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/DagSemProc.08161.7</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
