<?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 alias-offset.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/alias-offset.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/alias-offset.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>01a48535 - [MC][WebAssembly] Fix provisional values for data alias relocations</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/alias-offset.s#01a48535</link>
        <description>[MC][WebAssembly] Fix provisional values for data alias relocationsWhen calculating the symbol offsets to write as provisitonal valuesin object files we are only interested in the offset of the symbolitself.  For aliases this offset already includes the offset of thebase symbol.The testin question was added back in https://reviews.llvm.org/D87407but I believe the expectations here were incorrect.   sym_a livesat offset 4 and sym_b lives 4 bytes into that (should be 8).The addresses of the 3 symbosl in this object file are:foo  : 0sym_a: 4sym_b: 8Differential Revision: https://reviews.llvm.org/D96234

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/alias-offset.s</description>
        <pubDate>Mon, 08 Feb 2021 02:51:42 +0000</pubDate>
        <dc:creator>Sam Clegg &lt;sbc@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>9c7b5808 - [WebAssembly][MC] Fix computation of relative symbol offset</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/alias-offset.s#9c7b5808</link>
        <description>[WebAssembly][MC] Fix computation of relative symbol offsetFor relative symbols, add its offset when computing relocation value.Also, warn on unsupported absolute symbols.Differential Revision: https://reviews.llvm.org/D87407

            List of files:
            /llvm-project-15.0.7/llvm/test/MC/WebAssembly/alias-offset.s</description>
        <pubDate>Wed, 09 Sep 2020 01:17:05 +0000</pubDate>
        <dc:creator>Dominic Chen &lt;d.c.ddcc@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
