On Wed, Oct 10, 2012 at 3:12 AM, Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > On 10/09/2012 07:34 PM, Jonathan Neuschäfer wrote: >> >> This is required for producing valid LLVM bitcode. >> >> Cc: Pekka Enberg <penberg@xxxxxxxxxx> >> Cc: Christopher Li <sparse@xxxxxxxxxxx> >> Cc: Jeff Garzik <jgarzik@xxxxxxxxxx> >> Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> >> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx> >> --- >> sparse-llvm.c | 17 ++++++++++++++++- >> validation/backend/loop2.c | 13 +++++++++++++ >> 2 files changed, 29 insertions(+), 1 deletion(-) >> create mode 100644 validation/backend/loop2.c > > Looks sane... but I did not verify whether or not this reordering is safe Ditto. Jonathan, care to explain why you think it is safe? I still don't know Sparse's linearized IR well enough to convince myself this is OK. -- 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
