On Tue, Sep 12, 2017 at 8:44 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Tue, Sep 12, 2017 at 2:34 AM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: >> It's not the problem. >> I tested it on a ppc64le (power8) machine while I investigated the >> problem. So let's say that it's solved/tested for ppc64. Then what >> about all the other models & archs? > > For problem like this one happen on the host side of the package, > I don't have a magic solution either. I guess we will just fix the > bugs that we know. Then let other people who has the access to > those model & archs do the testing and report back. > > Mean while, we can make it easy to enable and disable > llvm, similar to a config file. The user don't have to patch > sparse in order to disable sparse-llvm compiling. Hence the patch. I think you should take it for master. -- 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
