llvm dev - Nov 2018 - [DWARF] Why epilogue_begin was not emitted?

Hello,

I found that prologue_end flag is emitted in dwarf debug information by the most
of llvm backend but epilogue_begin flag is never.
Please tell me why the specification is like this. I think this is asymmetry.
And I would also like to know how lldb find the end of function body without
epilogue_begin flag.

Thank you,
Tetsuya Ooka

Generally DWARF support is added on an as-needed basis, if no one working
on LLVM's DWARF support had a need to support a consumer that benefited
from such information, it's usually not implemented.

So usually there's not some specific aversion to a feature, but only a lack
of need/motivation to implement it.

I guess maybe existing debuggers have figured out the epilogue
heuristically well enough?

On Thu, Nov 15, 2018 at 8:50 PM Tetsuya Ooka via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hello,
>
> I found that prologue_end flag is emitted in dwarf debug information by
> the most of llvm backend but epilogue_begin flag is never.
> Please tell me why the specification is like this. I think this is
> asymmetry.
> And I would also like to know how lldb find the end of function body
> without epilogue_begin flag.
>
> Thank you,
> Tetsuya Ooka
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181116/f48b2dab/attachment-0001.html>