similar to: Xapian ported to WebAssembly for use in web browser

Okay, so where should I send questions for WebAssembly? Is it this mailing list or a different one? I want to ask about how to compile WebAssembly modules with Clang directly, without Emscripten, for situations like what I have currently where I have a problem with generating WebAssembly and/or JavaScript glue code (I have a problem with the gen_struct_info stuff; I asked on the Emscripten

Has anyone attempted to compile R (probably without any OS bindings) to WebAssembly / Emscripten? If so, how far did you get? (would be crazy awesome if you could get all the way to a ggplot bitmap output). If not, is this a waste of time or is there some daylight to doing this? [[alternative HTML version deleted]]

This was some time ago: https://stat.ethz.ch/pipermail/r-devel/2013-May/066724.html So probably not hopeless, but I would think it is a lot of work. Gabor On Wed, Feb 20, 2019 at 8:17 AM Todd Wilder <wildert at gmail.com> wrote: > > Has anyone attempted to compile R (probably without any OS bindings) to > WebAssembly / Emscripten? If so, how far did you get? (would be crazy >

As I recall, the major blocker is that R links against a number of other things (notably BLAS, pcre, etc) so while technically possible (?) I suppose, the universe of things you'd have to compile over and then get working is much larger than just the R internals. I think most people who consider this (including me years ago, as well as the poster of Gabor's message to rdevel) hit that

> > This seems interesting, I have a few questions: > > > Has the ISA been finalized yet or is it still a work in progress? Will > there be a fixed number of registers? > The design document has a high-level idea of the ISA, or rather of the AST we're thinking of going with: https://github.com/WebAssembly/design/blob/master/AstSemantics.md The final encoding isn't

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

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 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

I have successfully installed coda in R, and I am also able to read output from a Bugs run into coda. When I try to plots from CODA Output Analysis Menu, I do however _get_ problems: CODA Output Analysis Menu ************************* 1:Plots 2:Statistics 3:List/Change Options 4:Return to Main Menu Selection: 1 Error: "missing" illegal use of missing Quitting CODA.... Do you

Hello all, WebAssembly [0] its a new virtual ISA being designed to efficiently run compiled code in web browsers and other things, starting with C/C++, and eventually many other languages [1]. WebAssembly distinguishes itself from other virtual ISAs with optimizations to reduce download size and decode time, strong portability and predictability invariants (for example, the base has no undefined

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'm also interested in this warning as I have received it when compiling libopus for WebAssembly using Emscripten and have an open ticket (just saw that you responded to it, thanks for that!) https://stackoverflow.com/questions/49537429/building-compiling-opus-libopus-in-emscripten-with-optimization/ ​ -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, I'm currently looking for a VoIP platform to support the following features: Caller ID Call Waiting with caller ID Call Hold/Retrieve Three-way conference Calling Line Identity Presentation Call back last missed call Last called number redial User line locking/Call Barring (all current levels) Itemised bill Call Forward Call Forward on No Reply Call Forward on Busy Call Forward

Thanks Timothy. Media Source Extensions were much easier and high-level than using WebAssembly with the Web Audio API. Unfortunately, MSE does not support MIME "audio/ogg" and I had to put my OpusFiles into a WebM container file. What could we do to get MSE support for Ogg Opus files? I created this issue if it helps: https://github.com/w3c/media-source/issues/245. Would be happy to

Hello, I am new to R on Linux (and to LINUX), running a 1.9.1 on a Linux MDK10.0. When updating or installing different packages, I get messages like this (under), the package doesn't install. Can anyone help me? I know this is all to little information, but I don't know were to start. I think there is something wrong in how or were the C++ or fortran compilator is installed?? Thanks, Geir

Dan Gohman <sunfish at mozilla.com> writes: >> Sorry, I meant why that didn't work with ELF (or what else didn't). >> > > The standard executable WebAssembly format does not use ELF, for numerous > reasons, most visibly that ELF is designed for sparse decoding -- headers > contain offsets to arbitrary points in the file, while WebAssembly's format > is

Chris McGowan wrote: > All thoughts and contributions are welcome, and I'm planning to add a > seeking feature using HTTP range requests: > https://github.com/AnthumChris/opus-stream-decoder/issues/1 You may also be interested in <https://github.com/brion/ogv.js/> (if you're not already aware of it). There might be some useful collaboration possible. > ~140-220K Wasm

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

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 >

On 19/09/2007, Daniel Aleksandersen <aleksandersen+xiphlists@runbox.com> wrote: > On Wednesday 19. September 2007 19:02:06 Ian Malone wrote: > > Daniel Aleksandersen wrote: > > > Attached is a much improved version of yesterday's draft. Introducing > > > the audio:collection:artwork element to deal with album cover graphics > > > and such. > >