Priyanka Panigrahi via llvm-dev
2019-Dec-02 04:54 UTC
[llvm-dev] How to print stack frames after generating assembly from llc
Hello, I am generating an assembly code (.s file) throught llc tool. Is it possible to modify the .s file? I want to print the stack frame to console or to an output file for a particular function and print specific register values at particular breakpoints. Any pointers would be appreciated. Thank you for your time. Regards, Priyanka -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191202/75c6522e/attachment.html>
David Blaikie via llvm-dev
2019-Dec-02 15:53 UTC
[llvm-dev] How to print stack frames after generating assembly from llc
Not exactly sure I understand your question - but you can edit the .s file yourself/manually, but I guess that's not what you're asking for. You're wondering if there are any command line arguments to llc, etc, that'd cause it to print comments (or stderr, or something else) with stack frame descriptions? Not that I know of. You might be able to modify LLVM to add that functionality, though - I've no idea how hard that might be. There is someone who's proposing adding some changes to llvm-objdump that would print out variable location information from the DWARF in the assembly listing ( https://reviews.llvm.org/D70720 ) which might cover your use case? On Sun, Dec 1, 2019 at 11:54 PM Priyanka Panigrahi via llvm-dev < llvm-dev at lists.llvm.org> wrote:> Hello, > > I am generating an assembly code (.s file) throught llc tool. Is it > possible to modify the .s file? > > I want to print the stack frame to console or to an output file for a > particular function and print specific register values at particular > breakpoints. Any pointers would be appreciated. > > Thank you for your time. > > Regards, > Priyanka > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://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/20191202/be20410c/attachment.html>