On 14 August 2017 at 17:25, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Mon, Aug 14, 2017 at 6:17 PM, Dibyendu Majumdar > <mobile@xxxxxxxxxxxxxxx> wrote: >> On 14 August 2017 at 17:15, Luc Van Oostenryck >> <luc.vanoostenryck@xxxxxxxxx> wrote: >>> On Sun, Aug 13, 2017 at 10:20 PM, Dibyendu Majumdar >>> <mobile@xxxxxxxxxxxxxxx> wrote: >>>>> Care to send some examples you have problems with? >>>> >>>> Sure - you already know this one: >>>> >>>> https://github.com/dibyendumajumdar/dmr_c/blob/master/tests/bugs/simplifybug.c >>>> >>>> https://github.com/dibyendumajumdar/dmr_c/blob/master/tests/minilua/minilua.c >>>> >>> >>> OK, I just checked on the paranoia.c and once the global initializations >>> are removed sparse-llvm has not more problems when using all the >>> needed fixes. An updated tree can be found as usual at: >>> git://github.com/lucvoo/sparse.git sssa-next >>> >> >> Were you able to run the code generated by Sparse-LLVM - or are you >> saying that it compiled without errors? > > The former. More specifically that you can generate the LLVM bytecode > for the whole files and then see the IR with llvm-dis. > Okay thanks. I already have a working Sparse-LLVM and have more fixes than are in your tree. So my interest is really in getting the Sparse linearized code correct as that is where I now find all the issues are. I will look at merging your sssa-mini patches to dmrC. I had a quick look - presumably the ptrmap ought to be hash table? Anyway I have to make changes to avoid global state - in dmrC allocators are not global. Regards Dibyendu -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
