<?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 objdump.s</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9647a6f7 - [WebAssembly] Added initial type checker to MC Assembler</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#9647a6f7</link>
        <description>[WebAssembly] Added initial type checker to MC AssemblerThis to protect against non-sensical instruction sequences being assembled,which would either cause asserts/crashes further down, or a Wasm module being output that doesn&apos;t validate.Unlike a validator, this type checker is able to give type-errors as part of the parsing process, which makes the assembler much friendlier to be used by humans writing manual input.Because the MC system is single pass (instructions aren&apos;t even stored in MC format, they are directly output) the type checker has to be single pass as well, which means that from now on .globaltype and .functype decls must come before their use. An extra pass is added to Codegen to collect information for this purpose, since AsmPrinter is normally single pass / streaming as well, and would otherwise generate this information on the fly.A `-no-type-check` flag was added to llvm-mc (and any other tools that take asm input) that surpresses type errors, as a quick escape hatch for tests that were not intended to be type correct.This is a first version of the type checker that ignores control flow, i.e. it checks that types are correct along the linear path, but not the branch path. This will still catch most errors. Branch checking could be added in the future.Differential Revision: https://reviews.llvm.org/D104945

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Mon, 07 Jun 2021 19:10:47 +0000</pubDate>
        <dc:creator>Wouter van Oortmerssen &lt;aardappel@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>52e240a0 - [WebAssembly] Remove exnref and br_on_exn</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#52e240a0</link>
        <description>[WebAssembly] Remove exnref and br_on_exnThis removes `exnref` type and `br_on_exn` instruction. This iseffectively NFC because most uses of these were already removed in theprevious CLs.Reviewed By: dschuff, tlivelyDifferential Revision: https://reviews.llvm.org/D94041

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Sat, 26 Dec 2020 04:23:33 +0000</pubDate>
        <dc:creator>Heejin Ahn &lt;aheejin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>ecd6d725 - [test] llvm/test/: change llvm-objdump single-dash long options to double-dash options</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#ecd6d725</link>
        <description>[test] llvm/test/: change llvm-objdump single-dash long options to double-dash optionsAs announced here: http://lists.llvm.org/pipermail/llvm-dev/2019-April/131786.htmlGrouped option syntax (POSIX Utility Conventions) does not play well with -long-optionA subsequent change will reject -long-option.

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Sun, 15 Mar 2020 23:17:52 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>71e2ca6e - [llvm-objdump] -d: print `00000000 &lt;foo&gt;:` instead of `00000000 foo:`</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#71e2ca6e</link>
        <description>[llvm-objdump] -d: print `00000000 &lt;foo&gt;:` instead of `00000000 foo:`The new behavior matches GNU objdump. A pair of angle brackets makes tests slightly easier.`.foo:` is not unique and thus cannot be used in a `CHECK-LABEL:` directive.Without `-LABEL`, the CHECK line can match the `Disassembly of section`line and causes the next `CHECK-NEXT:` to fail.```Disassembly of section .foo:0000000000001634 .foo:```Bdragon: &lt;&gt; has metalinguistic connotation. it just &quot;feels right&quot;Reviewed By: rupprechtDifferential Revision: https://reviews.llvm.org/D75713

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Thu, 05 Mar 2020 22:18:38 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>9f96a58c - [WebAssembly] Rename except_ref type to exnref</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#9f96a58c</link>
        <description>[WebAssembly] Rename except_ref type to exnrefSummary:We agreed to rename `except_ref` to `exnref` for consistency with otherreference types inhttps://github.com/WebAssembly/exception-handling/issues/79. This alsorenames WebAssemblyInstrExceptRef.td to WebAssemblyInstrRef.td in orderto use the file for other reference types in future.Reviewers: dschuffSubscribers: sbc100, jgravelle-google, hiraditya, sunfish, jfb, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D64703llvm-svn: 366145

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Mon, 15 Jul 2019 22:49:25 +0000</pubDate>
        <dc:creator>Heejin Ahn &lt;aheejin@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>1a91cb04 - [WebAssembly] Make disassembler always emit most canonical name.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#1a91cb04</link>
        <description>[WebAssembly] Make disassembler always emit most canonical name.Summary:There are a few instructions that all map to the same opcode, sowhen disassembling, we have to pick one. That was just the first onebefore (the except_ref variant in the case of &quot;call&quot;), now it is theone marked as IsCanonical in tablegen, or failing that, the shortestname (which is typically the &quot;canonical&quot; one).Also introduced a canonical &quot;end&quot; instruction for this purpose.Reviewers: dschuff, tlivelySubscribers: sbc100, jgravelle-google, aheejin, llvm-commits, sunfishTags: #llvmDifferential Revision: https://reviews.llvm.org/D57713llvm-svn: 353131

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Tue, 05 Feb 2019 01:19:45 +0000</pubDate>
        <dc:creator>Wouter van Oortmerssen &lt;aardappel@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0b3cf247 - [WebAssembly] Make segment/size/type directives optional in asm</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#0b3cf247</link>
        <description>[WebAssembly] Make segment/size/type directives optional in asmSummary:These were &quot;boilerplate&quot; that repeated information already presentin .functype and end_function, that needed to be repeated to Pleasethe particular way our object writing works, and missing them wouldgenerate errors.Instead, we generate the information for these automatically so theuser can concern itself with writing more canonical wasm functionsthat always work as expected.Reviewers: dschuff, sbc100Subscribers: jgravelle-google, aheejin, sunfish, llvm-commitsDifferential Revision: https://reviews.llvm.org/D57546llvm-svn: 353067

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Mon, 04 Feb 2019 18:03:11 +0000</pubDate>
        <dc:creator>Wouter van Oortmerssen &lt;aardappel@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>f3b762a0 - [WebAssembly] Fixed objdump not parsing function headers.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s#f3b762a0</link>
        <description>[WebAssembly] Fixed objdump not parsing function headers.Summary:objdump was interpreting the function header containing the localsdeclaration as instructions. To parse these without injecting targetspecific code in objdump, MCDisassembler::onSymbolStart was added tobe implemented by the WebAssembly implemention.WasmObjectFile now returns a code offset for the &quot;address&quot; of a symbol,rather than the index. This is also more in-line with what othertargets do.Also ensured that the AsmParser correctly puts each functionin its own segment to enable this test case.Reviewers: sbc100, dschuffSubscribers: jgravelle-google, aheejin, sunfish, rupprecht, llvm-commitsDifferential Revision: https://reviews.llvm.org/D56684llvm-svn: 351460

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/objdump.s</description>
        <pubDate>Thu, 17 Jan 2019 18:14:09 +0000</pubDate>
        <dc:creator>Wouter van Oortmerssen &lt;aardappel@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
