search for: emitstackprobecall

Displaying 4 results from an estimated 4 matches for "emitstackprobecall".

2015 Jul 28
0
[LLVMdev] Adding a stack probe function attribute
...estack is different from every other hardcoded thing in LLVM. Furthermore since calls to it can be elided it is not useful for clients to specify their own function, so they would just point it to whatever the platform stack probing function would be (replicating the ugly logic in X86FrameLowering::emitStackProbeCall). If LLVM in the future always inlined the call, the stack probe function would never be called and the attribute argument is useless. - > > On Sun, Jul 26, 2015 at 2:23 AM, John Kåre Alsaker > <john.mailinglists at gmail.com> wrote: >> >> Since David Majnemer doesn'...
2015 Jul 28
2
[LLVMdev] Adding a stack probe function attribute
...every other > hardcoded thing in LLVM. Furthermore since calls to it can be elided > it is not useful for clients to specify their own function, so they > would just point it to whatever the platform stack probing function > would be (replicating the ugly logic in > X86FrameLowering::emitStackProbeCall). If LLVM in the future always > inlined the call, the stack probe function would never be called and > the attribute argument is useless. > The difference between __probestack and __chkstk etc is that we are happy to call into existing interfaces that are somehow guaranteed by the enviro...
2015 Jul 27
3
[LLVMdev] Adding a stack probe function attribute
Yeah, the function attributes section of LangRef is a reasonable place to put stuff like this: http://llvm.org/docs/LangRef.html#function-attributes I think we should add this. I also know that LLILAC needs something like this as well. I propose the following: - Add a string attribute called "stack-probe-symbol"="foo". - The presence of this attribute indicates that stack
2015 Jul 28
1
[LLVMdev] Adding a stack probe function attribute
...hardcoded thing in LLVM. Furthermore since calls to it can be elided >> it is not useful for clients to specify their own function, so they >> would just point it to whatever the platform stack probing function >> would be (replicating the ugly logic in >> X86FrameLowering::emitStackProbeCall). If LLVM in the future always >> inlined the call, the stack probe function would never be called and >> the attribute argument is useless. > > > The difference between __probestack and __chkstk etc is that we are happy to > call into existing interfaces that are somehow gu...