On Tue, Jun 20, 2017 at 11:09:18AM -0700, Christopher Li wrote: > On Sun, Jun 18, 2017 at 1:11 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > Yes, sure. > > I would like to let it 'soak' a little bit more but I don't see > > well how it could be more tested. > > Understand. Do you want it on sparse-next while have it soaking? IIRC, one of the two patches need a small changes. I'll send you a pull request with the others few fixes. But I have first some cleanup to do and some retesting. > > I may try the kernel on some non-x86 archs but it won't be for > > today or tomorrow. There was some issues on ARM64. I also made two changes for freebsd & openbsd that were broken. > > I have also a patch series for the root cause of the 1st patch: > > the misplacement of phi-nodes. This series solve all sort of > > problems but it's not the kind of changes for this release: > > it's radical changes to some pretty fundamental things and it's > > diffstat is: "16 files changed, 679 insertions(+), 476 deletions(-)" > > excluding all the changes in the testcases. This will need to > > wait for after the release and it's not yet ready anyway, not > > even close to. > > Thanks I was wondering how complicate is the proper fix like. > That is good to know. Yes it's definitively not release material but I've fixed a blocking issue, so I'll post the series soon. But for the moment, I focus on the release. > > > > For the release, I also want the other fix I posted this week, > > the one titled "fix: add missing examine in evaluate_dereference()" > > which is much more straight-forward. > > I have pull your "for-chris" branch into sparse-next. Yes, I saw. Thanks. -- Luc -- 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
