Dibyendu Majumdar

Possible memory leak

3

I am getting this report from ASAN: ``` Direct leak of 4832 byte(s) in 151 object(s) allocated from: #0 0x7fbc939fc638 in __interceptor_malloc (/lib64/libasan.so.5+0x10c638) #1 0x7fbc934d2739 in gen_malloc /home/dylan/github/ravi/mir/mir-gen.c:238 #2 0x7fbc934f4470...

First use of MIR JIT in Ravi

38

Hi @vnmakarov I implemented a PoC using MIR JIT as the backend for Ravi. You can see this here: https://github.com/dibyendumajumdar/ravi/commit/4e445f46bfe239db6a85d4b338dc343cd5103229 So far I have only tested basics ... looks promising....

Feature request: MIR to LLVM IR translator

3

I believe that a MIR to LLVM IR translator would be very useful. Following is potential use case: ``` C -> MIR -> machine code (tier 1) C -> MIR...

MIR_link error 'import of undefined item memcpy'

2

I am hitting an issue when running MIR_link() - it complains: 'import of undefined item memcpy'. My C code doesn't use memcpy as far as I can see - so...

Question: c2mir_init and c2mir_finish - should be called only once per context?

2

As with MIR_gen init/finish I assume c2mir init/finish functions should also be called only once per context?

Please use long long type for 64-bit integer and long is not portable

4

In MSVC the 'long' type is 32-bits, hence it is preferrable to use 'long long' when repesenting 64-bit integers. This affects https://github.com/vnmakarov/mir/blob/master/c2mir/x86_64/mirc-x86_64-linux.h at least - I haven't checked if this...

Enabling -Wall generates lots of warnings when compiling

1

I noticed that in my builds there were lots of warning messages - but if I used the supplied Makefile then none. I suppose this is because the supplied Makefile...

In some places sparse code uses long type. This should be changed to int or long long type as long type is not portable

The sparse simplification phase is error prone and given there is no active compiler experts looking at this it is unlikely to improve. Given Jit backends such as llvm and...

In this option the linearizer will be excluded, as will any JIT backends.