[PATCH] Change objectsize intrinsic to accept different address spaces.
arsenm2 at gmail.com
Thu Oct 3 22:17:29 PDT 2013
On Oct 3, 2013, at 18:27 , Eric Christopher <echristo at gmail.com> wrote:
> Right. I was trying to figure out if it's because we actually expected
> the memory coming in to be something other than addrspace 0. I.e. does
> the fortify checking really make sense for that case?
I would like it if someday if the bounds checking and similar passes were GPU friendly. Debugging out of bounds LDS writes isn't fun
More information about the llvm-commits