Pankaj Gode
2013-Apr-29 06:02 UTC
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
Hi All, Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' optimization), a local variable gets declared and initialized inside the basic blocks it is used in. Is there anyway I can avoid this ? This is with reference with my previous question. http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html Regards, Pankaj -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130428/c2deb1ea/attachment.html>
Eric Christopher
2013-Apr-29 06:54 UTC
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
There was a patch committed the other day that should, at least, work around some of the behavior you describe. Optimized debug info is an area that's being worked on in ToT and previous releases are particularly bad. I'd use that. -eric On Mon, Apr 29, 2013 at 7:02 AM, Pankaj Gode <godepankaj at yahoo.com> wrote:> Hi All, > > Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' > optimization), a local variable gets declared and initialized inside the > basic blocks it is used in. > Is there anyway I can avoid this ? > > This is with reference with my previous question. > http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html > > > Regards, > Pankaj > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Pankaj Gode
2013-Apr-29 12:01 UTC
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
Hi Eric, Thanks for patch information. I have checked the patch with my code and I see that it works. But when I extract the variable and check the metadata information to retrieve the scope information, I do not get exact scope, after optimization. As you said that this is a work in progress, so can we expect full version on this in llvm3.3 release ? Regards, Pankaj ________________________________ From: Eric Christopher <echristo at gmail.com> To: Pankaj Gode <godepankaj at yahoo.com>; Adrian Prantl <aprantl at apple.com> Cc: llvm Developers <llvmdev at cs.uiuc.edu> Sent: Monday, April 29, 2013 12:24 PM Subject: Re: [LLVMdev] LowerDbgDeclare results in redeclaration of local variable There was a patch committed the other day that should, at least, work around some of the behavior you describe. Optimized debug info is an area that's being worked on in ToT and previous releases are particularly bad. I'd use that. -eric On Mon, Apr 29, 2013 at 7:02 AM, Pankaj Gode <godepankaj at yahoo.com> wrote:> Hi All, > > Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' > optimization), a local variable gets declared and initialized inside the > basic blocks it is used in. > Is there anyway I can avoid this ? > > This is with reference with my previous question. > http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html > > > Regards, > Pankaj > > _______________________________________________ > LLVM Developers mailing list > 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/20130429/29f3b34d/attachment.html>
Apparently Analagous Threads
- [LLVMdev] LowerDbgDeclare results in redeclaration of local variable
- [LLVMdev] LowerDbgDeclare results in redeclaration of local variable
- [LLVMdev] collect end line number for scope
- [LLVMdev] collect end line number for scope
- [LLVMdev] collect end line number for scope