<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Implement global variables in WebAssembly"
href="https://bugs.webkit.org/show_bug.cgi?id=149031#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Implement global variables in WebAssembly"
href="https://bugs.webkit.org/show_bug.cgi?id=149031">bug 149031</a>
from <span class="vcard"><a class="email" href="mailto:sukolsak@gmail.com" title="Sukolsak Sakshuwong <sukolsak@gmail.com>"> <span class="fn">Sukolsak Sakshuwong</span></a>
</span></b>
<pre>Global variables have been removed from the MVP.
"Mutable global variables
In the MVP, there are no global variables; C/C++ global variables are stored in linear memory and thus accessed through normal linear memory operations. Dynamic linking will add some form of immutable global variable analogous to "symbols" in native binaries. In some cases, though, it may be useful to have a fully mutable global variable which lives outside linear memory. This would allow more aggressive compiler optimizations (due to better alias information). If globals are additionally allowed array types, significant portions of memory could be moved out of linear memory which could reduce fragmentation issues. Langauges like FORTRAN which limit aliasing would be one use case. C/C++ compilers could also determine that some global variables never have their address taken." (<a href="https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#mutable-global-variables">https://github.com/WebAssembly/design/blob/master/FutureFeatures.md#mutable-global-variables
"Postpone adding globals until dynamic linking" (<a href="https://github.com/WebAssembly/design/issues/154">https://github.com/WebAssembly/design/issues/154</a>)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>