W3C home > Mailing lists > Public > public-webassembly@w3.org > May 2016

Re: Query: Using llvm 's Webassembly backend

From: JF Bastien <jfb@google.com>
Date: Tue, 3 May 2016 08:40:19 -0700
Message-ID: <CABdywOca1O8cePw=SeCXaOkkkMR5a5gRF+GVtgqjcLJPX5m+KA@mail.gmail.com>
To: Sandeep Dasgupta <sdasgup3@illinois.edu>
Cc: public-webassembly@w3.org
Hi Sandeep,

This list has quite a few people, we usually operate on the github
repositories, and through IRC. I think the problem is between emscripten
and upstream LLVM, I recommend filing a bug in emscripten's bug tracker
<https://github.com/kripken/emscripten>.

Thanks,

JF

On Mon, May 2, 2016 at 11:43 AM, Sandeep Dasgupta <sdasgup3@illinois.edu>
wrote:

> Hello All,
>
> I tried using llvm "WebAssembly" backend to generate llvm bc to be  fed
> into emscripten.
>
>
> warning: Linking two modules of different data layouts:
>> '${HOME}/.emscripten_cache/libc.bc' is
>> 'e-p:32:32-i64:64-v128:32:128-n32-S128' whereas 'func_1.bc' is
>> 'e-m:e-p:32:32-i64:64-n32:64-S128'
>>
>> warning: Linking two modules of different target triples:
>> ${HOME}/.emscripten_cache/libc.bc' is 'asmjs-unknown-emscripten' whereas
>> 'func_1.bc' is 'wasm32-wasm32-wasm32'
>>
>
> Please let me know if llvm's webassembly backend  is not compatible with
> emscripten yet ?
>
>
>
> Regards,
>
> Sandeep
>
>
>
>
>
>
>
Received on Tuesday, 3 May 2016 15:40:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:55:31 UTC