[Mono-list] Mono LLVM

[Andres G. Aragoneses]

An alternative to what the OP might want to achieve then is maybe JSIL? 
https://github.com/kevingadd/JSIL

On 03/04/13 21:14, Rodrigo Kumpera wrote:
> This was a bug on the last released mono and we've fixed it.
>
> Besides that, no, it's not possible to use emscripten with mono's llvm
> output for a lot of reasons.
> The output embeds calls to the mono runtime and some trampilines.
> Mono use a custom LLVM with custom IR operations and that won't work on
> emscripten without some work on their end.
>
>
> On Wed, Apr 3, 2013 at 11:44 AM, Александр Гурьянов <caiiiycuk at gmail.com
> <mailto:caiiiycuk at gmail.com>> wrote:
>
>     Hi all. It is possible to compile program into llvm ir for use it in
>     emscripten? Now i try to compile aot with llvm, but got error:
>
>     mono --aot=full --llvm Game.exe
>     Mono Ahead of Time compiler - compiling assembly Game.exe
>     * Assertion at image-writer.c:2177, condition `fp' not met
>
>     Stacktrace:
>
>
>     Native stacktrace:
>
>          mono() [0x80e6431]
>          [0xb773a40c]
>          [0xb773a424]
>          /lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb75471df]
>          /lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb754a825]
>          mono() [0x82189f7]
>          mono() [0x8218a73]
>          mono() [0x80fa2b3]
>          mono() [0x80cee35]
>          mono(mono_main+0xd82) [0x80c0112]
>          mono() [0x805bac8]
>          /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb75324d3]
>          mono() [0x805bbc5]
>
>     Debug info from gdb:
>
>     [New LWP 21083]
>     [New LWP 21082]
>     [Thread debugging using libthread_db enabled]
>     Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
>     0xb773a424 in __kernel_vsyscall ()
>        Id   Target Id         Frame
>        3    Thread 0xb71ccb40 (LWP 21082) "mono" 0xb773a424 in
>     __kernel_vsyscall ()
>        2    Thread 0xb668db40 (LWP 21083) "mono" 0xb773a424 in
>     __kernel_vsyscall ()
>     * 1    Thread 0xb7517700 (LWP 21081) "mono" 0xb773a424 in
>     __kernel_vsyscall ()
>
>     Thread 3 (Thread 0xb71ccb40 (LWP 21082)):
>     #0  0xb773a424 in __kernel_vsyscall ()
>     #1  0xb76cd96b in pthread_cond_wait@@GLIBC_2.3.2 () at
>     ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
>     #2  0x0822ba97 in ?? ()
>     #3  0x08225db9 in ?? ()
>     #4  0x0822a252 in ?? ()
>     #5  0xb76c9d4c in start_thread (arg=0xb71ccb40) at pthread_create.c:308
>     #6  0xb7607d3e in clone () at
>     ../sysdeps/unix/sysv/linux/i386/clone.S:130
>
>     Thread 2 (Thread 0xb668db40 (LWP 21083)):
>     #0  0xb773a424 in __kernel_vsyscall ()
>     #1  0xb76cfcc5 in sem_wait@@GLIBC_2.1 () at
>     ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/sem_wait.S:80
>     #2  0x0820fa38 in mono_sem_wait ()
>     #3  0x0815696c in ?? ()
>     #4  0x081df5cd in ?? ()
>     #5  0x0820a033 in ?? ()
>     #6  0x0822b888 in ?? ()
>     #7  0xb76c9d4c in start_thread (arg=0xb668db40) at pthread_create.c:308
>     #8  0xb7607d3e in clone () at
>     ../sysdeps/unix/sysv/linux/i386/clone.S:130
>
>     Thread 1 (Thread 0xb7517700 (LWP 21081)):
>     #0  0xb773a424 in __kernel_vsyscall ()
>     #1  0xb76d09db in read () at ../sysdeps/unix/syscall-template.S:82
>     #2  0x080e65fc in ?? ()
>     #3  <signal handler called>
>     #4  0xb773a424 in __kernel_vsyscall ()
>     #5  0xb75471df in __GI_raise (sig=6) at
>     ../nptl/sysdeps/unix/sysv/linux/raise.c:64
>     #6  0xb754a825 in __GI_abort () at abort.c:91
>     #7  0x082189f7 in ?? ()
>     #8  0x08218a73 in ?? ()
>     #9  0x080fa2b3 in ?? ()
>     #10 0x080cee35 in ?? ()
>     #11 0x080c0112 in mono_main ()
>     #12 0x0805bac8 in ?? ()
>     #13 0xb75324d3 in __libc_start_main (main=0x805b9d0, argc=4,
>     ubp_av=0xbfd8f444, init=0x823e300, fini=0x823e370,
>     rtld_fini=0xb774a270 <_dl_fini>, stack_end=0xbfd8f43c) at
>     libc-start.c:226
>     #14 0x0805bbc5 in ?? ()
>
>     =================================================================
>     Got a SIGABRT while executing native code. This usually indicates
>     a fatal error in the mono runtime or one of the native libraries
>     used by your application.
>     =================================================================
>
>
>     Thanks.
>
>     _______________________________________________
>     Mono-list maillist  - Mono-list at lists.ximian.com
>     <mailto:Mono-list at lists.ximian.com>
>     http://lists.ximian.com/mailman/listinfo/mono-list
>
>
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>