<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in opt-record.proftext</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>8f96e82c - Add an option to save the backend-produced YAML optimization record to a file</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/Inputs/opt-record.proftext#8f96e82c</link>
        <description>Add an option to save the backend-produced YAML optimization record to a fileThe backend now has the capability to save information from optimizations, thesame information that can be used to generate optimization diagnostics but inmachine-consumable form, into an output file. This can be enabled when usingopt (see r282539), and this change enables it when using clang. The idea isthat other tools will be able to consume these files, and perhaps incombination with the original source code, produce various kinds ofoptimization reports for users (and for compiler developers).We now have at-least two tools that can consume these files:  * tools/llvm-opt-report  * utils/opt-viewerUsing the flag -fsave-optimization-record will cause the YAML file to begenerated; the file name will be based on the output file name (if we&apos;re using-c or -S and have an output name), or the input file name. When we&apos;re usingCUDA, or some other offloading mechanism, separate files are generated for eachbackend target. The output file name can be specified by the user using-foptimization-record-file=filename.Differential Revision: https://reviews.llvm.org/D25225llvm-svn: 283834

            List of files:
            /llvm-project-15.0.7/clang/test/CodeGen/Inputs/opt-record.proftext</description>
        <pubDate>Tue, 11 Oct 2016 00:26:09 +0000</pubDate>
        <dc:creator>Hal Finkel &lt;hfinkel@anl.gov&gt;</dc:creator>
    </item>
</channel>
</rss>
