On Thu, Jun 21, 2012 at 7:08 PM, Xi Wang <xi.wang@xxxxxxxxx> wrote: > On Jun 21, 2012, at 6:00 PM, Christopher Li wrote: > https://github.com/xiw/sparse/commit/7072002 > > Then we have: > > and.64 %r2 <- %arg1, $0x1fffffff > cast.32 %r3 <- (64) %r2 > ret.32 %r3 > > Does this make sense? Or should we just provide an option to turn > off all sparse simplifications, since backends usually have their own > optimization passes? Adding the cast from 64 to 32 bit make sense. The sparse checker can still benefit from the simplifications. I think it is OK we turn off those simplifications for sparse-llvm back end. I want to have this module that, the back end can pick to chose what kind of simplification/optimization done to the linearized instructions. I think the sparse-llvm back end need a different code path in the front end for things like GEP any way. Chris -- 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
