[PATCH] [GC] improve testing around gc.relocate and catch a bug

[Ramkumar Ramachandra]

(After watching the LLVMDev talk): Did you mean that the result of the relocate is unused, and hence no code is generated? If I did `%a = gc.relocate(...)`, and then used `%a` in another `gc.statepoint` call, then a `mov` will be generated like in statepoint-stack-usage.ll? The `mov` is generated because it's assuming that the gc is relocating the base, and then returning a new derived with some offset (= the original derived - base) for use with the second `gc.statepoint`?


http://reviews.llvm.org/D6824

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/