similar to: Generating exported wasm functions

wasm-ld is currently unable to link a shared wasm library (generated with `wasm-ld --shared`) with .o files and produce a working executable. I'm curious if there's a fundamental reason for this, or is this simply something that wasn't needed and could be implemented if needed. I think this could be done by - Resolving "GOT.mem" and "GOT.func" imports and

Can you link to docs about the wasm object format? (both relocatable and executable) Also, traditional object file linkers are primarily concerned with concatenating binary blobs with small amount of patching of said binary blobs based on computed virtual (memory) addresses. Or perhaps to put it another way, what traditional object file linkers do is construct program images meant to be mapped

Hi llvmers, As you may know, work has been progressing on the experimental WebAssembly backend in llvm. However, there is currently not a good linking story. Most the of existing linking strategies (i.e. those in the emscripten toolchain) involve bitcode linking and whole program compilation at link time. To improve this situation I've been working on adding a wasm backend for lld. My

Sean Silva <chisophugis at gmail.com> writes: > On Mon, Jul 3, 2017 at 11:12 AM, Rafael Avila de Espindola < > rafael.espindola at gmail.com> wrote: > >> Sam Clegg via llvm-dev <llvm-dev at lists.llvm.org> writes: >> >> >> Can you elaborate on semantically what the linker is actually doing for >> >> wasm? >> > >> >

Hi, Sorry if you've seen this message before on llvm.discourse.group or elsewhere -- I've been trying to get to the bottom of this for a while now and asked about this in a few different platforms before. I'm currently trying to debug a bug in a LLVM-generated Wasm code. The bug could be in the code that generates LLVM (rustc) or in the LLVM, I'm not sure yet. LLVM IR and Wasm

Hi Sam, First, I want to know the symbol resolution semantics. I can imagine that that is set in stone yet, but just that you guys are still discussing what would be the best semantics or file format for the linkable wasm object file. I think by knowing more about the format and semantics, we can give you guys valuable feedback, as we've been actively working on the linker for a few years

Apologies if there is a better forum for these questions. Please redirect me if so. I’ve been using the clang/wasm-ld tools to experiment with some basic examples, and there’s a couple things I’m wrestling with. 1) How to denote a function as the “start” function (https://webassembly.github.io/spec/core/binary/modules.html#start-section) 2) How to avoid the defaulted __heap_base global. I’ve

On Mon, Jul 10, 2017 at 4:13 PM, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Sorry for the belated response. I was on vacation last week. A couple of > thoughts on this patch and the story of webassembly linking. And I'm about to be on (mostly) vacation for next 3 weeks :) > > - This patch adds a wasm support as yet another major architecture besides >

Sam Clegg via llvm-dev <llvm-dev at lists.llvm.org> writes: >> Can you elaborate on semantically what the linker is actually doing for >> wasm? > > You are correct that the wasm linker does have more work to do than a > traditional linker. There are more sections that the linker will need > to re-construct fully. This is because there is more high level >

Hi Sam, Thanks for your answer! Sorry I didn't really know how to process, but this issue block me to make some legacy C code works without having some glue with a bit static lib ;( (The change have really low risk) The changes I used locally to make dlopen/dlclose et dlsym mechanism works :) : Index: wasm/Writer.cpp =================================================================== ---

Hi, when linking with lld/wasm with a symbol like: @_typeinfo__rtti_te_Module6_d_Test = private constant i8* bitcast (@_rtti_te_Module6_d_Test to i8*), section "ELRTTLRR", align 4 How do I get the start and end of the ELRTTLRR section? LLD doesn't seem to emit that info, nor does it define a __start_ELRTTLRR/__stop_ELRTTLRR section?

Hello, The table generated by lld (Wasm target) have a max size. So this make impossible to add some others functions in the table . As for the moment only one Table is available in WAsm this is the only way to add function in a dynamic way. Having a none static size of the table is useful for a kind dynamic loader/inker at run-time: by adding some exported functions coming from another

I'm seeing the following fail on Linux x86-64, for the last couple weeks at least. This is from 'ninja check-all'. -David FAIL: lld :: wasm/function-index.test (1941 of 1955) ******************** TEST 'lld :: wasm/function-index.test' FAILED ******************** Script: -- : 'RUN: at line 1'; /build/x86_64/bin/llc -filetype=obj

David, That's right, WebAssembly does not have a way to conditionally use a feature or even do runtime feature testing right now. It's on our roadmap of things to design and standardize, but it is still a long way off. > Another direction would be to require the features to be specified consistently for all components of the build, I guess - if that's the net effect anyway. Would

@Jonathan Goodwin: Do I have to use a flag to tell it where the LLVM include files are? And would it be easier to do that in the CMake GUI? Please tell me how you had it find the include files if that may help me. ________________________________ From: Jonathan Goodwin <jondgoodwin at gmail.com> Sent: Wednesday, November 28, 2018 6:24 AM To: zturner at google.com Cc: Osman Zakir; llvm-dev

Hi, I am using LLVM as the backend in a small hobby compiler project I'm working on. I plan to support all platforms that LLVM supports (limited by my available hardware only). As far as I can tell, there are different linkers for the various host systems out there (the output of 'lld' if you invoke it on Arch Linux): lld is a generic driver. Invoke ld.lld (Unix), ld64.lld

I think most people are using ninja to do the build. You can still use the Visual Studio generator for the IDE experience while doing build from ninja. I know there are a couple of people who build from inside of Visual Studio, but it's a pretty small number, and I don't think they are targeting WebAssembly. On Tue, Nov 27, 2018 at 12:46 PM Osman Zakir via llvm-dev < llvm-dev at

If anyone is integrating Opus audio into a web or JavaScript application, I wrote a WebAssembly Opus decoder that uses libopusfile to decode Opus files in chunks using the JavaScript Streams API. This decoder can begin decoding after receiving the Opus headers and first audio data page: https://github.com/AnthumChris/opus-stream-decoder All thoughts and contributions are welcome, and I'm

Hello. Excuse me. Why CMakeLists.txt from llvm-3.9.1.src does not contain WebAssembly target? So, it is like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) but not like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ Webassembly X86

I cannot reproduce this error, but this could be real. David, is this reproducible every time or is this flaky? On Mon, Jan 7, 2019 at 5:03 PM Heejin Ahn via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello David, > > I use x86_64 and it works on my machine. I also can't find this error on > LLVM buildbot page. I'd appreciate if you help me reproduce the problem.