On Wed, Mar 08, 2017 at 11:38:22PM +0000, Dibyendu Majumdar wrote: > Hi Luc, > > On 8 March 2017 at 06:53, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > On Tue, Mar 07, 2017 at 07:31:34AM +0000, Dibyendu Majumdar wrote: > >> >> Here 'values' has been defined above as external global, whereas it > >> >> should be allocated on the stack. > >> > > >> > Mmmh, I'll need to look a bit further at this one. > >> > > >> > >> It appears that sparse-llvm only creates a local stack object for each > >> OP_PHI instruction. What should be the general approach for > >> identifying local stack objects in sparse linearized output? > > > > I've looked a bit at this and there is several issues at hand. > > It's also not something LLVM specific. > > So I can't answer to this for now. Hopefully, I'll be able to tell > > you more in a few days. > > > > Thank you for looking into this. It would be good to know what issues > you have discovered. The issues is about which symbols are used, which ones don't need to be allocated because all their use are via pseudos, ... A lot of infrastructure already exist for it bit is incomplete or wrong. Also, I first focus to finalize the previous issues with the NULLs, ADDs, CALLs, ... -- Luc Van Oostenryck -- 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
