similar to: [LLVMdev] LLVM IR execution in JavaScript

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] LLVM IR execution in JavaScript"

2013 Jan 02
0
[LLVMdev] LLVM IR execution in JavaScript
----- Original Message ----- > From: "Sebastian Redl" <sebastian.redl at getdesigned.at> > To: "Eli Bendersky" <eliben at google.com> > Cc: "Alon Zakai" <azakai at mozilla.com>, "llvmdev" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, January 2, 2013 11:24:33 AM > Subject: Re: [LLVMdev] LLVM IR execution in JavaScript >
2013 Jan 02
3
[LLVMdev] LLVM IR execution in JavaScript
On 02.01.2013, at 19:51, Eli Bendersky wrote: >> I compiled parts of LLVM to JavaScript using emscripten and made a demo of parsing and executing LLVM assembly, >> >> http://kripken.github.com/llvm.js/demo.html >> >> Basically you enter some LLVM IR, press a button and see the output of compiling and running it, directly in the browser. >> >> This was
2013 Jan 02
0
[LLVMdev] LLVM IR execution in JavaScript
> I compiled parts of LLVM to JavaScript using emscripten and made a demo of parsing and executing LLVM assembly, > > http://kripken.github.com/llvm.js/demo.html > > Basically you enter some LLVM IR, press a button and see the output of compiling and running it, directly in the browser. > > This was done mainly as a fun hacking project over the holidays, but I'm posting it
2013 Jan 02
2
[LLVMdev] LLVM IR execution in JavaScript
On 02.01.2013, at 20:37, Alon Zakai wrote: > > > ----- Original Message ----- >> From: "Sebastian Redl" <sebastian.redl at getdesigned.at> >> >> It would be awesome to combine the llvm.org demo with the in-browser >> emscripten (or possibly a server-side emscripten) so that the user >> can execute his snippets in the browser. >>
2013 Jan 02
0
[LLVMdev] LLVM IR execution in JavaScript
----- Original Message ----- > From: "Sebastian Redl" <sebastian.redl at getdesigned.at> > To: "Alon Zakai" <azakai at mozilla.com> > Cc: "llvmdev" <llvmdev at cs.uiuc.edu>, "Eli Bendersky" <eliben at google.com> > Sent: Wednesday, January 2, 2013 11:44:27 AM > Subject: Re: [LLVMdev] LLVM IR execution in JavaScript >
2011 Dec 17
0
[LLVMdev] Emscripten: LLVM => JavaScript
On Fri, Dec 16, 2011 at 7:14 PM, Alon Zakai <azakai at mozilla.com> wrote: > > > ----- Original Message ----- >> From: "Eli Friedman" <eli.friedman at gmail.com> >> To: "Alon Zakai" <azakai at mozilla.com> >> Cc: llvmdev at cs.uiuc.edu >> Sent: Thursday, December 15, 2011 7:02:34 PM >> Subject: Re: [LLVMdev] Emscripten:
2011 Dec 16
2
[LLVMdev] Emscripten: LLVM => JavaScript
Hi everyone, I wanted to mention a project using LLVM: Emscripten. Emscripten is an open source LLVM to JavaScript compiler, http://emscripten.org https://github.com/kripken/emscripten/ There are various demos linked to on the wiki (the first link), of various large C/C++ codebases compiled to JS and running on the web, like Python, Bullet, Poppler, etc. Emscripten is not a
2011 Dec 17
3
[LLVMdev] Emscripten: LLVM => JavaScript
----- Original Message ----- > From: "Eli Friedman" <eli.friedman at gmail.com> > To: "Alon Zakai" <azakai at mozilla.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Thursday, December 15, 2011 7:02:34 PM > Subject: Re: [LLVMdev] Emscripten: LLVM => JavaScript > On Thu, Dec 15, 2011 at 4:10 PM, Alon Zakai <azakai at mozilla.com> > wrote: >
2011 Dec 16
0
[LLVMdev] Emscripten: LLVM => JavaScript
On Thu, Dec 15, 2011 at 4:10 PM, Alon Zakai <azakai at mozilla.com> wrote: > On that topic, I see there is an LLVM users page, > > http://llvm.org/Users.html > > - what is the procedure for suggesting adding a project to > there? Send a patch to llvm-commits. > The third issue I want to raise is regarding closer > integration with LLVM. Right now, Emscripten uses
2013 Feb 13
2
Vorbis encoding using JavaScript
Hello, First of all, I am a complete newblet to anything dealing with audio (a lot of the vocabulary is still rather mysterious to me). I also don't often program in C so please don't throw too many stones if my workflow is less than ideal. :) I would like to port the vorbis encoder to JavaScript. Instead of porting everything by hand from ground up, which would take who-knows-how-long,
2011 Dec 12
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
On Sun, Dec 11, 2011 at 2:19 PM, Rafael Ávila de Espíndola < rafael.espindola at gmail.com> wrote: > On 08/12/11 03:56 PM, Ivan Krasin wrote: > > Hi llvm team! > > > > I'm currently working on the extended version of llvm-ld, which has an > > ability to check if all the symbols present (and fail if some symbols > > are not resolved), treat archives in
2011 Dec 14
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
> $ llc bar.bc -filetype=obj -o bar.o > $ clang -shared -o bar.so bar.o > $ clang -use-gold-plugin foo.o bar.so -o t > > Is that correct? In particular, "lld t" should show a dependency on bar. > Any particular reason for not adding this to the plugin api? > > The result is a native .so here. My goal is to have a bitcode result. > >
2014 Mar 04
9
[LLVMdev] Upstreaming PNaCl's IR simplification passes
The PNaCl project has implemented various IR simplification passes that simplify LLVM IR by lowering complex features to simpler features. We'd like to upstream some of these IR passes to LLVM. We'd like to explore if this acceptable, and if so, how we should go about doing this. The immediate reason is that Emscripten is reusing PNaCl's IR passes for its new "fastcomp"
2010 Oct 03
4
[LLVMdev] JavaScript Backend
Hi all, Over the past couple weeks, I've been putting together a JavaScript backend for LLVM. At this point, I believe I've got reasonable implementations for all the instructions, primitives and derived types. I haven't gotten around to most of the intrinsics but I thought it would be a good idea to start getting some feedback before going much further. If anyone has the time and
2012 May 07
0
[LLVMdev] Using LLVM for decompiling.
> -----Original Message----- > On Behalf Of James Courtier-Dutton > To: John Criswell > > On 7 May 2012 16:31, John Criswell <criswell at illinois.edu> wrote: > > On 5/7/12 5:47 AM, James Courtier-Dutton wrote: > >> > >> Hi, > >> > >> I am writing a decompiler. I was wondering if some of LLVM could be > >> used for a
2010 Oct 03
0
[LLVMdev] JavaScript Backend
On Oct 2, 2010, at 8:11 PM, David LaPalomento wrote: > Hi all, > Over the past couple weeks, I've been putting together a JavaScript > backend for LLVM. At this point, I believe I've got reasonable > implementations for all the instructions, primitives and derived > types. I haven't gotten around to most of the intrinsics but I thought > it would be a good idea to
2011 Dec 11
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
On 08/12/11 03:56 PM, Ivan Krasin wrote: > Hi llvm team! > > I'm currently working on the extended version of llvm-ld, which has an > ability to check if all the symbols present (and fail if some symbols > are not resolved), treat archives in the right way (link all the object > files in the archive if it's specified as the regular input, not as -l) Is that the
2015 Jan 20
2
FW: flac (encoder, analyzer, decoder) tool now (also) available in JavaScript‏
Hi List! On flac--l I was advised to cross-post to this list. So here is an extended version: After compiling opusenc.js to JavaScript [1], now the flac tool is also available [2][3], too. s/Check out/Clone/ https://github.com/Rillke/flac.js ! I am slightly nervous about its license, the GPL and what CloudFlare is doing: It's melting a lot of content together into one file (but not
2013 Jan 02
1
[LLVMdev] LLVM IR execution in JavaScript
On 02.01.2013, at 20:50, Alon Zakai wrote: > I agree both are useful approaches. I went with clientside-everything in this demo because I work on that stuff and like it ;) Oh, I agree that it is awesome. It just froze my browser completely for several seconds just compiling the Hello World program. Sebastian
2011 Dec 08
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
Hi llvm team! I'm currently working on the extended version of llvm-ld, which has an ability to check if all the symbols present (and fail if some symbols are not resolved), treat archives in the right way (link all the object files in the archive if it's specified as the regular input, not as -l) and the most important to my project feature: to link against bitcode "shared