Not working (no output)

[4ntoine]

I've cloned repository, opened demo.html and clicked "compile and run" button without changing the source code and i see green field with no any output. On demo page (http://kripken.github.io/llvm.js/demo.html) i can see "hello, world" green output. So what's wrong? What is LLVM.js project status?

[4ntoine]

If i made an error in .ll code it shows me red error, so bitcode is processed. If i fix an error, output field becomes green but previous error text is not cleared

[4ntoine]

tested on chrome, mac osx maverics

[kripken]

The project is not active from my perspective, sorry - i have no time to spend on it.

[4ntoine]

No problem. Can you explain in brief, how can i compile *.js files from LLVM/Clang sources? I believe it's not just like git clone LLVM/Clang sources and run ./emconfigure ./emmake, right?

[kripken]

yes, basically just like porting any other project using emscripten. but, you will need to handle tblgen which is built and run natively. need a parallel native build, and to take the executables from that. i think i mentioned that in the readme

[4ntoine]

ok i have finished emmake make (fixed all the "all-target" issues). i can't see any .bc files produced. what should i do after i finished emmake?

[kripken]

it should emit bitcode files. could have suffix .o or .so or .a

On Tue, Sep 23, 2014 at 9:14 AM, Anton Smirnov notifications@github.com
wrote:

ok i have finished emmake make (fixed all the "all-target" issues). i
can't see any .bc files produced. what should i do after i finished emmake?

—
Reply to this email directly or view it on GitHub
#2 (comment).

[4ntoine]

yes, i can see a lot if .o files in Release+Asserts. But in common build .o files are packed in lib*.a (using ar) and how to get according llvm static libs for JS?

[4ntoine]

Libs

oh, i can see also ./Release+Asserts/lib/lib*.a files which are not ar files - probably they are expected files. Since they are not common ar files (

MBA-Anton:build_local asmirnov$ lipo -info ../build_emscripten/Release+Asserts/lib/libclang.a
Segmentation fault: 11

) are they llvm bitcode archive?

Should they be renamed to .bc (as in projects build guide http://kripken.github.io/emscripten-site/docs/compiling/Building-Projects.html)?

Executables

Also in ./Release+Asserts/bin i can see files (f.e. lli, llc) which are not marked as executables. Are they llvm bitcode too? in common build they are interpreter and compiler accordingly

Final steps

I can't see "llvm" file in ./Release+Asserts/bin to be renamed to llvm.bc (https://github.com/kripken/llvm.js/blob/master/llvm.bc).

Thanks for helping me do it finally! I will publish my "update to LLVM 3.5 instructions" after all.

[piranna]

Great work @4ntoine! :-) Did you be able to compile clang? This would help to have toolchain on NodeOS! :-)

[4ntoine]

No, unfortunately

2014-10-02 16:15 GMT+06:00 Jesús Leganés Combarro notifications@github.com
:

Great work @4ntoine https://github.com/4ntoine! :-) Did you be able to
compile clang? This would help to have toolchain on NodeOS! :-)

—
Reply to this email directly or view it on GitHub
#2 (comment).

[piranna]

It's a shame, it would be really useful... :-(

[4ntoine]

Probably i will be able to do it if having answers to my questions

[piranna]

Let's wait, then :-)