[LLVMdev] Debug information for outlined routine

[sebastien deldon (PGI)]

Hi David,

Thanks for the quick reply. I guess the problem can become even more complex when more than one routine are outlined from original routine.
In general most OpenMP implementations performs outlining for parallel region. So it is likely that current implementation in LLVM doesn't support debugging ?

Seb

From: David Blaikie [mailto:dblaikie at gmail.com]
Sent: Monday, January 27, 2014 5:12 PM
To: sebastien deldon (PGI); Eric Christopher
Cc: llvmdev
Subject: Re: [LLVMdev] Debug information for outlined routine



On Mon, Jan 27, 2014 at 4:24 AM, sebastien deldon (PGI) <sebastien.deldon at pgroup.com<mailto:sebastien.deldon at pgroup.com>> wrote:
Hi all,

I would like to know how can I express debug information for an outlined function using llvm debug metadata.
I mean I have a function f() and part of its code is outlined in a new function g() . I would like to generate llvm debug metadata so that when stepping in g() the debugger step in original sources lines from f() routine ?

Given that LLVM has no current support for outlining I don't think we've addressed the issue of how to represent that in LLVM's IR metadata (indeed I don't even know off-hand how DWARF handles this).


Thanks for your help
Seb
________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________

_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu<mailto:LLVMdev at cs.uiuc.edu>         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140127/f5da4125/attachment.html>