search for: getstackcookieloc

...is designed for); 3) TLS has a different semantic from address space ( http://llvm.org/docs/CodeGenerator.html#x86-address-spaces-supported). > That said, the basic idea of keeping around the way to access the TLS > variable is pretty easy, we do some amount of this in > TargetLowering::getStackCookieLocation, but we might just need to come up > with a new interface there that returns the address of the stack local load > rather than an offset from an address space. > I also found a similar case - getSafeStackPointerLocation(). On X86 it's implemented in terms of address space (simila...

I found a bit weird to use address space for this, since the offset of getting stack_guard in TCB is, unfortunately, negative: https://github.com/gcc-mirror/gcc/blob/master/gcc/config/rs6000/linux64.h#L610 In my understanding an address space is referring to a segment register (-on powerpc 32bit; or SLB entry on powerpc 64bit?) with a non-negative offset value, so that it's actually accessing

+nlewycky On Mon, Nov 17, 2014 at 9:36 AM, Volodymyr Kuznetsov <vova.kuznetsov at epfl.ch > wrote: > Hi Kostya, > > On Sat, Nov 15, 2014 at 1:53 PM, Volodymyr Kuznetsov < > vova.kuznetsov at epfl.ch> wrote: > > Do you think moving the pass to lib/Transform/Instrumentation but > > scheduling it during code generation would make sense ? If so, we'll >

...E_ATTR(NoRedZone); HANDLE_ATTR(NoImplicitFloat); diff --git a/lib/Target/X86/X86ISelLowering.cpp b/lib/Target/X86/X86ISelLowering.cpp index d8ffc36..e231979 100644 --- a/lib/Target/X86/X86ISelLowering.cpp +++ b/lib/Target/X86/X86ISelLowering.cpp @@ -1942,6 +1942,33 @@ bool X86TargetLowering::getStackCookieLocation(unsigned &AddressSpace, return true; } +bool X86TargetLowering::getUnsafeStackPtrLocation(unsigned &AddressSpace, + unsigned &Offset) const { + if (Subtarget->isTargetLinux()) { + if (Subtarget->is64Bit()) { + //...