Hi Luc, On 12 August 2017 at 20:28, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > On Sat, Aug 12, 2017 at 8:51 PM, Dibyendu Majumdar > <mobile@xxxxxxxxxxxxxxx> wrote: >> >> ..., I would like to try out your new SSA construction approach. >> Please let me know if this is complete (i.e. functional). > > It's more than simply functional, it seems to work pretty well: > - it passes the testsuite > - it doesn't crash while using it on the kernel or any of my tests > (I have plenty of tests I can't upstream or doesn't make sense > to be upstreamed) > - the generated code handle correctly the placement of phi-nodes > - the generated code handle correctly undefined vars/pseudos > - it's a bit faster than the current sparse and use less memory > > But: > - it needs more testing > - code needs some polish here & there > - it's not a panacea for all current issues. > > In my opinion, it's a HUGE step forward. > That sounds very good. >> I had a look >> at the branch above, but not all commits appeared to be related to the >> SSA construction, so any pointer to the list of changes I should pick >> would be very helpful. > > True, the first commits are some small improvement, bug fixes or > even optimization fixes I need for testing during development. > > Currently, I'm busy to aggregate the others changes, the LLVM ones > and friends. There are a few merge conflicts to solve but not much. > The next step will be to make the SSA more usable. > Okay please let me know when you are ready for me to try and incorporate this work. I will be finished merging the RC5 changes in the next few days. 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