|
|
6a20676fa9
|
Actually unmap the code after it's done being used
|
2019-02-28 17:20:18 -08:00 |
|
|
|
359ac5abec
|
Connect part of the llvm backend to the runtime
|
2019-02-28 13:18:00 -08:00 |
|
|
|
d4ae5cdd40
|
Get function addresses from llvm-compiled code
|
2019-02-28 12:31:39 -08:00 |
|
|
|
5d77769381
|
Hopefully finish the memory manager implementation for llvm RuntimeDyLd
|
2019-02-27 17:21:20 -08:00 |
|
|
|
4f833876e0
|
Start work on object loader using llvm's RuntimeDyld api.
|
2019-02-25 18:08:06 -08:00 |
|
|
|
2a913f5663
|
Implement table, partial call_indirect
|
2019-02-22 17:34:55 -08:00 |
|
|
|
108973dabe
|
Start producing object files with llvm
|
2019-02-15 16:02:20 -08:00 |
|
|
|
73b4f7d337
|
Implement memory and global operations
|
2019-02-14 18:08:20 -08:00 |
|
|
|
8827830aba
|
implement load* and store* instructions
|
2019-02-14 15:13:58 -08:00 |
|
|
|
2572a0259b
|
Get control flow working (fingers crossed)
|
2019-02-12 18:02:00 -08:00 |
|
|
|
5ee19e55a5
|
Add some branching instructions
|
2019-02-11 19:34:04 -08:00 |
|
|
|
327e3a4a1a
|
Implement many wasm instructions
|
2019-02-09 15:53:40 -08:00 |
|
