<?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 AnalysisManagerTest.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>491d2701 - [mlir] Use has_value instead of hasValue (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#491d2701</link>
        <description>[mlir] Use has_value instead of hasValue (NFC)

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Wed, 13 Jul 2022 07:57:02 +0000</pubDate>
        <dc:creator>Kazu Hirata &lt;kazu@google.com&gt;</dc:creator>
    </item>
<item>
        <title>3b7c3a65 - Revert &quot;Don&apos;t use Optional::hasValue (NFC)&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#3b7c3a65</link>
        <description>Revert &quot;Don&apos;t use Optional::hasValue (NFC)&quot;This reverts commit aa8feeefd3ac6c78ee8f67bf033976fc7d68bc6d.

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Sat, 25 Jun 2022 18:56:50 +0000</pubDate>
        <dc:creator>Kazu Hirata &lt;kazu@google.com&gt;</dc:creator>
    </item>
<item>
        <title>aa8feeef - Don&apos;t use Optional::hasValue (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#aa8feeef</link>
        <description>Don&apos;t use Optional::hasValue (NFC)

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Sat, 25 Jun 2022 18:55:57 +0000</pubDate>
        <dc:creator>Kazu Hirata &lt;kazu@google.com&gt;</dc:creator>
    </item>
<item>
        <title>58ceae95 - [mlir:NFC] Remove the forward declaration of FuncOp in the mlir namespace</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#58ceae95</link>
        <description>[mlir:NFC] Remove the forward declaration of FuncOp in the mlir namespaceFuncOp has been moved to the `func` namespace for a little over a month, theusing directive can be dropped now.

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Mon, 18 Apr 2022 18:53:47 +0000</pubDate>
        <dc:creator>River Riddle &lt;riddleriver@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>5e50dd04 - [mlir] Rework the implementation of TypeID</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#5e50dd04</link>
        <description>[mlir] Rework the implementation of TypeIDThis commit restructures how TypeID is implemented to ideally avoidthe current problems related to shared libraries. This is done by changingthe &quot;implicit&quot; fallback path to use the name of the type, instead of usinga static template variable (which breaks shared libraries). The major downside to thisis that it adds some additional initialization costs for the implicit path. Given theuse of type names for uniqueness in the fallback, we also no longer allow typesdefined in anonymous namespaces to have an implicit TypeID. To simplify definingan ID for these classes, a new `MLIR_DEFINE_EXPLICIT_INTERNAL_INLINE_TYPE_ID` macrowas added to allow for explicitly defining a TypeID directly on an internal class.To help identify when types are using the fallback, `-debug-only=typeid` can beused to log which types are using implicit ids.This change generally only requires changes to the test passes, which are all definedin anonymous namespaces, and thus can&apos;t use the fallback any longer.Differential Revision: https://reviews.llvm.org/D122775

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Thu, 31 Mar 2022 00:00:37 +0000</pubDate>
        <dc:creator>River Riddle &lt;riddleriver@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>36550692 - [mlir] Move the Builtin FuncOp to the Func dialect</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#36550692</link>
        <description>[mlir] Move the Builtin FuncOp to the Func dialectThis commit moves FuncOp out of the builtin dialect, and into the Funcdialect. This move has been planned in some capacity from the momentwe made FuncOp an operation (years ago). This commit handles thefunctional aspects of the move, but various aspects are left untouchedto ease migration: func::FuncOp is re-exported into mlir to reducethe actual API churn, the assembly format still accepts the unqualified`func`. These temporary measures will remain for a little while tosimplify migration before being removed.Differential Revision: https://reviews.llvm.org/D121266

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 08 Mar 2022 03:16:03 +0000</pubDate>
        <dc:creator>River Riddle &lt;riddleriver@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8f66ab1c - Replace OwningModuleRef with OwningOpRef&lt;ModuleOp&gt;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#8f66ab1c</link>
        <description>Replace OwningModuleRef with OwningOpRef&lt;ModuleOp&gt;This addresses a TODO in BuiltinOps.h.Reviewed By: rriddleDifferential Revision: https://reviews.llvm.org/D118574

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Sun, 30 Jan 2022 02:41:10 +0000</pubDate>
        <dc:creator>Sanjoy Das &lt;sanjoy@playingwithpointers.com&gt;</dc:creator>
    </item>
<item>
        <title>be0a7e9f - Adjust &quot;end namespace&quot; comment in MLIR to match new agree&apos;d coding style</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#be0a7e9f</link>
        <description>Adjust &quot;end namespace&quot; comment in MLIR to match new agree&apos;d coding styleSee D115115 and this mailing list discussion:https://lists.llvm.org/pipermail/llvm-dev/2021-December/154199.htmlDifferential Revision: https://reviews.llvm.org/D115309

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 07 Dec 2021 18:27:58 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>cd94f18e - [mlir] Pass AnalysisManager as optional parameter to analysis ctor, so it can request any other analysis as dependency</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#cd94f18e</link>
        <description>[mlir] Pass AnalysisManager as optional parameter to analysis ctor, so it can request any other analysis as dependencyDifferential Revision: https://reviews.llvm.org/D100274

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Sat, 10 Apr 2021 16:38:11 +0000</pubDate>
        <dc:creator>Butygin &lt;ivan.butygin@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>65fcddff - [mlir][BuiltinDialect] Resolve comments from D91571</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#65fcddff</link>
        <description>[mlir][BuiltinDialect] Resolve comments from D91571* Move ops to a BuiltinOps.h* Add file comments

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Thu, 19 Nov 2020 18:43:12 +0000</pubDate>
        <dc:creator>River Riddle &lt;riddleriver@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>73ca690d - [mlir][NFC] Remove references to Module.h and Function.h</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#73ca690d</link>
        <description>[mlir][NFC] Remove references to Module.h and Function.hThese includes have been deprecated in favor of BuiltinDialect.h, which contains the definitions of ModuleOp and FuncOp.Differential Revision: https://reviews.llvm.org/D91572

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 17 Nov 2020 08:38:10 +0000</pubDate>
        <dc:creator>River Riddle &lt;riddleriver@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b7382ed3 - [MLIR] Extend Symbol verification to reject public symbol declarations.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#b7382ed3</link>
        <description>[MLIR] Extend Symbol verification to reject public symbol declarations.- Extend the Symbol interface with `isDeclaration` to identify operations that declare  a symbol as opposed to define it.- Extend verification to disallow public declarations as per the discussion in   https://llvm.discourse.group/t/rfc-symbol-definition-declaration-x-visibility-checks/2140- Adopt the new interface for `FuncOp` and fix test and code to not have/create public  function declarations.Differential Revision: https://reviews.llvm.org/D91456

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Fri, 13 Nov 2020 21:04:53 +0000</pubDate>
        <dc:creator>Rahul Joshi &lt;jurahul@google.com&gt;</dc:creator>
    </item>
<item>
        <title>e7021232 - Remove global dialect registration</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#e7021232</link>
        <description>Remove global dialect registrationThis has been deprecated for &gt;1month now and removal was announced in:https://llvm.discourse.group/t/rfc-revamp-dialect-registration/1559/11Differential Revision: https://reviews.llvm.org/D86356

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Fri, 23 Oct 2020 20:19:35 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>6a726358 - Revert &quot;Remove global dialect registration&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#6a726358</link>
        <description>Revert &quot;Remove global dialect registration&quot;This reverts commit b22e2e4c6e420b78a8a4c307f0cf002f51af9590.Investigating broken builds

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Fri, 23 Oct 2020 21:26:32 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b22e2e4c - Remove global dialect registration</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#b22e2e4c</link>
        <description>Remove global dialect registrationThis has been deprecated for &gt;1month now and removal was announced in:https://llvm.discourse.group/t/rfc-revamp-dialect-registration/1559/11Differential Revision: https://reviews.llvm.org/D86356

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Fri, 23 Oct 2020 20:19:35 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c39c2161 - Rename AnalysisManager::slice in AnalysisManager::nest (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#c39c2161</link>
        <description>Rename AnalysisManager::slice in AnalysisManager::nest (NFC)The naming wasn&apos;t reflecting the intent of this API, &quot;nest&quot; is aligningit with the pass manager API.

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Fri, 28 Aug 2020 20:17:38 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f9dc2b70 - Separate the Registration from Loading dialects in the Context</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#f9dc2b70</link>
        <description>Separate the Registration from Loading dialects in the ContextThis changes the behavior of constructing MLIRContext to no longer load globallyregistered dialects on construction. Instead Dialects are only loaded explicitlyon demand:- the Parser is lazily loading Dialects in the context as it encounters themduring parsing. This is the only purpose for registering dialects and not loadthem in the context.- Passes are expected to declare the dialects they will create entity from(Operations, Attributes, or Types), and the PassManager is loading Dialects intothe Context when starting a pipeline.This changes simplifies the configuration of the registration: a compiler onlyneed to load the dialect for the IR it will emit, and the optimizer isself-contained and load the required Dialects. For example in the Toy tutorial,the compiler only needs to load the Toy dialect in the Context, all the others(linalg, affine, std, LLVM, ...) are automatically loaded depending on theoptimization pipeline enabled.To adjust to this change, stop using the existing dialect registration: theglobal registry will be removed soon.1) For passes, you need to override the method:virtual void getDependentDialects(DialectRegistry &amp;registry) const {}and registery on the provided registry any dialect that this pass can produce.Passes defined in TableGen can provide this list in the dependentDialects listfield.2) For dialects, on construction you can register dependent dialects using theprovided MLIRContext: `context.getOrLoadDialect&lt;DialectName&gt;()`This is useful if a dialect may canonicalize or have interfaces involvinganother dialect.3) For loading IR, dialect that can be in the input file must be explicitlyregistered with the context. `MlirOptMain()` is taking an explicit registry forthis purpose. See how the standalone-opt.cpp example is setup:  mlir::DialectRegistry registry;  registry.insert&lt;mlir::standalone::StandaloneDialect&gt;();  registry.insert&lt;mlir::StandardOpsDialect&gt;();Only operations from these two dialects can be in the input file. To include allof the dialects in MLIR Core, you can populate the registry this way:  mlir::registerAllDialects(registry);4) For `mlir-translate` callback, as well as frontend, Dialects can be loaded inthe context before emitting the IR: context.getOrLoadDialect&lt;ToyDialect&gt;()Differential Revision: https://reviews.llvm.org/D85622

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 18 Aug 2020 20:01:19 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>e75bc5c7 - Revert &quot;Separate the Registration from Loading dialects in the Context&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#e75bc5c7</link>
        <description>Revert &quot;Separate the Registration from Loading dialects in the Context&quot;This reverts commit d14cf45735b0d09d7d3caf0824779520dd20ef10.The build is broken with GCC-5.

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Wed, 19 Aug 2020 00:32:30 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d14cf457 - Separate the Registration from Loading dialects in the Context</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#d14cf457</link>
        <description>Separate the Registration from Loading dialects in the ContextThis changes the behavior of constructing MLIRContext to no longer load globallyregistered dialects on construction. Instead Dialects are only loaded explicitlyon demand:- the Parser is lazily loading Dialects in the context as it encounters themduring parsing. This is the only purpose for registering dialects and not loadthem in the context.- Passes are expected to declare the dialects they will create entity from(Operations, Attributes, or Types), and the PassManager is loading Dialects intothe Context when starting a pipeline.This changes simplifies the configuration of the registration: a compiler onlyneed to load the dialect for the IR it will emit, and the optimizer isself-contained and load the required Dialects. For example in the Toy tutorial,the compiler only needs to load the Toy dialect in the Context, all the others(linalg, affine, std, LLVM, ...) are automatically loaded depending on theoptimization pipeline enabled.To adjust to this change, stop using the existing dialect registration: theglobal registry will be removed soon.1) For passes, you need to override the method:virtual void getDependentDialects(DialectRegistry &amp;registry) const {}and registery on the provided registry any dialect that this pass can produce.Passes defined in TableGen can provide this list in the dependentDialects listfield.2) For dialects, on construction you can register dependent dialects using theprovided MLIRContext: `context.getOrLoadDialect&lt;DialectName&gt;()`This is useful if a dialect may canonicalize or have interfaces involvinganother dialect.3) For loading IR, dialect that can be in the input file must be explicitlyregistered with the context. `MlirOptMain()` is taking an explicit registry forthis purpose. See how the standalone-opt.cpp example is setup:  mlir::DialectRegistry registry;  registry.insert&lt;mlir::standalone::StandaloneDialect&gt;();  registry.insert&lt;mlir::StandardOpsDialect&gt;();Only operations from these two dialects can be in the input file. To include allof the dialects in MLIR Core, you can populate the registry this way:  mlir::registerAllDialects(registry);4) For `mlir-translate` callback, as well as frontend, Dialects can be loaded inthe context before emitting the IR: context.getOrLoadDialect&lt;ToyDialect&gt;()Differential Revision: https://reviews.llvm.org/D85622

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 18 Aug 2020 20:01:19 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d84fe55e - Revert &quot;Separate the Registration from Loading dialects in the Context&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp#d84fe55e</link>
        <description>Revert &quot;Separate the Registration from Loading dialects in the Context&quot;This reverts commit e1de2b75501e5eaf8777bd5248382a7c55a44fd6.Broke a build bot.

            List of files:
            /llvm-project-15.0.7/mlir/unittests/Pass/AnalysisManagerTest.cpp</description>
        <pubDate>Tue, 18 Aug 2020 22:15:59 +0000</pubDate>
        <dc:creator>Mehdi Amini &lt;joker.eph@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
