Re: Why does tail call only unwind the current stack frame instead of resetting the current stack?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Sep 12, 2021 at 10:08 PM Hsuan-Chi Kuo <hsuanchikuo@xxxxxxxxx> wrote:
>
> No, I didn't hit this limit.
>
> The current implementation already keeps tracks of the number of tail
> calls which to me is the same effort of tracking the stack size. I was
> just wondering if there's any fundamental reason that you can't reset
> the stack directly. But it seems that there is not.

The tail_call unwinds the current stack frame.
See comment at line 3585 for details.

And please don't top post.



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux