[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-commits
Subject:    [PATCH] D58742: [WebAssembly] Remove uses of ThreadModel
From:       Sam Clegg via Phabricator via cfe-commits <cfe-commits () lists ! llvm ! org>
Date:       2019-02-28 19:13:05
Message-ID: a31a862954fd646b987ea282a62b18a8 () localhost ! localdomain
[Download RAW message or body]

sbc100 added a comment.

In D58742#1413979 <https://reviews.llvm.org/D58742#1413979>, @sunfish wrote:

> Wasm gives users reasons to want -mthread-model single that other architectures \
> don't, even when -matomics is enabled by default. 
> When shared memory is used, wasm requires modules to declare a max memory size, \
> which is a burden on applications that want to use dynamic amounts of memory. Wasm \
> is more sensitive to code size than most other architectures. And, interoperating \
> with single-threaded JS is easier from single-threaded wasm (JS has access to \
> SharedArrayBuffer and atomics, but not all JS wants to use that).


Yes, but I don't see how that is related to this change.   I don't think there is a \
plan to make `-matomics` the default, and even if we did users would be free to \
disable it.

My understanding is that the default for clang and llvm and lld for the foreseeable \
will be to target single threaded mode, with non-shared-memory.   This CL doesn't \
change that.


Repository:
  rLLD LLVM Linker

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D58742/new/

https://reviews.llvm.org/D58742



_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits


[prev in list] [next in list] [prev in thread] [next in thread]