<?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 access_specifiers.hlsl</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>0d6b574b - [HLSL] Adjust access specifier behavior</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/ParserHLSL/access_specifiers.hlsl#0d6b574b</link>
        <description>[HLSL] Adjust access specifier behaviorHLSL doesn&apos;t support access specifiers. This change has two components:1) Make default access for classes public2) Diagnose the use of access specifiers as a clang HLSL extensionAs long as the default behavior for access specifiers matches HLSL,allowing them to be used doesn&apos;t cause sourece incompatability withvalid code. As such enabling them as a clang extension seems like areasonable approach.Fixes #55124Reviewed By: aaron.ballmanDifferential Revision: https://reviews.llvm.org/D124487

            List of files:
            /llvm-project-15.0.7/clang/test/ParserHLSL/access_specifiers.hlsl</description>
        <pubDate>Thu, 28 Apr 2022 15:13:20 +0000</pubDate>
        <dc:creator>Chris Bieneman &lt;chris.bieneman@me.com&gt;</dc:creator>
    </item>
</channel>
</rss>
