Thanks for the clarification.
On Mon, Nov 12, 2018 at 3:09 PM wrote:
> On Mon, 12 Nov 2018 02:00:02 +0800, Carter Cheng said:
> > Thanks for the reply but the link doesn't quite answer the question. I am
> > wondering how the pointer is handled so that there is one per thread by
> the
> >
On Mon, 12 Nov 2018 02:00:02 +0800, Carter Cheng said:
> Thanks for the reply but the link doesn't quite answer the question. I am
> wondering how the pointer is handled so that there is one per thread by the
> compiler. I perhaps was under the perhaps mistaken impression that the
> stack pointer
Thanks for the reply but the link doesn't quite answer the question. I am
wondering how the pointer is handled so that there is one per thread by the
compiler. I perhaps was under the perhaps mistaken impression that the
stack pointer frame pointer management inside the compiler makes certain
On Sun, Nov 11, 2018 at 6:04 PM Carter Cheng wrote:
> I am wondering how the compiler divines which stack to use for function calls
> and placement of locals and arguments when a function call is made inside the
> kernel since the kernel has multiple call stacks. Are function calls handled
>
Hello,
I am wondering how the compiler divines which stack to use for function
calls and placement of locals and arguments when a function call is made
inside the kernel since the kernel has multiple call stacks. Are function
calls handled manually inside kernel code or is there something special