I think this is the same as
https://github.com/kripken/emscripten/issues/2244 ? Let's focus the
conversation there.

- Alon



On Thu, Mar 20, 2014 at 5:22 PM, Soeren Balko <[email protected]> wrote:

> Hi Alon,
>
> after I upped my emscripten installation to use the "fastcomp" option by
> default and setting up the LLVM backend as described in the Wiki (
> https://github.com/kripken/emscripten/wiki/LLVM-Backend), the final
> JavaScript generation phase crashes (see here:
> https://github.com/kripken/emscripten/issues/2244)
>
> DEBUG    root: emscript: llvm backend: 
> /home/balko/dev/libav.js/emscripten-fastcomp/build/Release/bin/llc 
> /tmp/tmprwoJAW/ffmpeg.bc -march=js -filetype=asm -o 
> /tmp/emscripten_temp/tmpsziB5y.4.js -O2
> 0  llc       0x0896f75f llvm::sys::PrintStackTrace(_IO_FILE*) + 47
> 1  llc       0x0896f9bf
> 2  llc       0x0896f3c4
> 3            0x40022400 __kernel_sigreturn + 0
> 4  llc       0x088ab1a7 llvm::Value::stripPointerCasts() + 23
> 5  llc       0x087983ab
> 6  llc       0x08799c26
> 7  llc       0x0879b703
> 8  llc       0x08897464 llvm::MPPassManager::runOnModule(llvm::Module&) + 596
> 9  llc       0x088975f3 llvm::PassManagerImpl::run(llvm::Module&) + 227
> 10 llc       0x08897686 llvm::PassManager::run(llvm::Module&) + 38
> 11 llc       0x0812ed3c
> 12 llc       0x08120df7 main + 247
> 13 libc.so.6 0x401be935 __libc_start_main + 245
> 14 llc       0x0812b599
> Stack dump:
> 0.  Program arguments: 
> /home/balko/dev/libav.js/emscripten-fastcomp/build/Release/bin/llc 
> /tmp/tmprwoJAW/ffmpeg.bc -march=js -filetype=asm -o 
> /tmp/emscripten_temp/tmpsziB5y.4.js -O2
> 1.  Running pass 'JavaScript backend' on module '/tmp/tmprwoJAW/ffmpeg.bc'.
> DEBUG    root:   emscript: llvm backend took 5.70895290375 seconds
> Traceback (most recent call last):
>   File "/home/balko/dev/libav.js/emscripten/emscripten.py", line 1433, in 
> <module>
>     _main(environ=os.environ)
>   File "/home/balko/dev/libav.js/emscripten/emscripten.py", line 1421, in 
> _main
>     temp_files.run_and_clean(lambda: main(
>   File "/home/balko/dev/libav.js/emscripten/tools/tempfiles.py", line 39, in 
> run_and_clean
>     return func()
>   File "/home/balko/dev/libav.js/emscripten/emscripten.py", line 1429, in 
> <lambda>
>     DEBUG_CACHE=DEBUG_CACHE,
>   File "/home/balko/dev/libav.js/emscripten/emscripten.py", line 1316, in main
>     jcache=jcache, temp_files=temp_files, DEBUG=DEBUG, 
> DEBUG_CACHE=DEBUG_CACHE)
>   File "/home/balko/dev/libav.js/emscripten/emscripten.py", line 761, in 
> emscript_fast
>     backend_output = open(temp_js).read()
> IOError: [Errno 2] No such file or directory: 
> '/tmp/emscripten_temp/tmpsziB5y.4.js'
> Traceback (most recent call last):
>   File "/home/balko/dev/libav.js/emscripten/emcc", line 1537, in <module>
>     final = shared.Building.emscripten(final, append_ext=False, 
> extra_args=extra_args)
>   File "/home/balko/dev/libav.js/emscripten/tools/shared.py", line 1333, in 
> emscripten
>     assert os.path.exists(filename + '.o.js') and len(open(filename + 
> '.o.js', 'r').read()) > 0, 'Emscripten failed to generate .js: ' + 
> str(compiler_output)
> AssertionError: Emscripten failed to generate .js:
> make: *** [/home/balko/dev/libav.js/bin/ffmpeg.js] Error 1
>
>
> As I could successfully compile that code before, this is presumably a bug
> in the new fastcomp option (i.e., the LLVM backend). I have made the LLVM
> bitcode files available on DropBox:
> https://dl.dropboxusercontent.com/u/97987244/bugs/emcc-0-basebc.bc and
> https://dl.dropboxusercontent.com/u/97987244/bugs/emcc-1-linktime.bc*. *Any
> clues?
>
> Thanks,
> Soeren
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to