<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in export-table-explicit.test</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9ac5620cb8548c0bd0150f0da68219dd3a5a657a - [WebAssembly] Rename WasmLimits::Initial to ::Minimum.  NFC.</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lld/test/wasm/export-table-explicit.test#9ac5620cb8548c0bd0150f0da68219dd3a5a657a</link>
        <description>[WebAssembly] Rename WasmLimits::Initial to ::Minimum.  NFC.This patch renames the &quot;Initial&quot; member of WasmLimits to the name usedin the spec, &quot;Minimum&quot;.In the core WebAssembly specification, the Limits data type has onerequired &quot;min&quot; member and one optional &quot;max&quot; member, indicating theminimum required size of the corresponding table or memory, and themaximum size, if any.Although the WebAssembly spec does instantiate locally-defined tablesand memories with the initial size being equal to the minimum size, itcan&apos;t impose such a requirement for imports.  It doesn&apos;t make sense torequire an initial size for a memory import, for example.  The compilercan only sensibly express the minimum and maximum sizes.Seehttps://github.com/WebAssembly/js-types/blob/master/proposals/js-types/Overview.md#naming-of-size-limitsfor a related discussion that agrees that the right name of &quot;initial&quot; is&quot;minimum&quot; when querying the type of a table or memory from JavaScript.(Of course it still makes sense for JS to speak in terms of an initialsize when it explicitly instantiates memories and tables.)Differential Revision: https://reviews.llvm.org/D99186

            List of files:
            /llvm-project/lld/test/wasm/export-table-explicit.test</description>
        <pubDate>Tue, 23 Mar 2021 13:46:32 +0000</pubDate>
        <dc:creator>Andy Wingo &lt;wingo@igalia.com&gt;</dc:creator>
    </item>
<item>
        <title>63393828078c382e8e69d9b8146372b70bbce20f - [WebAssembly] Add support for table linking to wasm-ld</title>
        <link>http://src.rcs.uwaterloo.ca:8080/source/history/llvm-project/lld/test/wasm/export-table-explicit.test#63393828078c382e8e69d9b8146372b70bbce20f</link>
        <description>[WebAssembly] Add support for table linking to wasm-ldThis patch adds support to wasm-ld for linking multiple table referencestogether, in a manner similar to wasm globals. The indirect functiontable is synthesized as needed.To manage the transitional period in which the compiler doesn&apos;t yetproduce TABLE_NUMBER relocations and doesn&apos;t residualize table symbols,the linker will detect object files which have table imports ordefinitions, but no table symbols. In that case it will synthesizesymbols for the defined and imported tables.As a change, relocatable objects are now written with table symbols,which can cause symbol renumbering in some of the tests. If no objectfile requires an indirect function table, none will be written to thefile. Note that for legacy ObjFile inputs, this test is conservative: aswe don&apos;t have relocs for each use of the indirecy function table, wejust assume that any incoming indirect function table should bepropagated to the output.Differential Revision: https://reviews.llvm.org/D91870

            List of files:
            /llvm-project/lld/test/wasm/export-table-explicit.test</description>
        <pubDate>Thu, 14 Jan 2021 09:15:56 +0000</pubDate>
        <dc:creator>Andy Wingo &lt;wingo@igalia.com&gt;</dc:creator>
    </item>
</channel>
</rss>
