This is maybe a minor issue, but it is obvious when one looks at debug info produced by clang. Such records are normally created by the code like this: Instruction->setDebugLoc(llvm::DebugLoc::get(Line, Column, Scope)); and it appears that Column is always zero. Yuri
Yaron Keren
2014-Jan-25 09:19 UTC
[LLVMdev] clang doesn't set code column in debug info records
Hi Yuri, You need to set clang::CodeGenOptions.DebugColumnInfo = 1; it's not enabled by default. Yaron 2014-01-25 Yuri <yuri at rawbw.com>> This is maybe a minor issue, but it is obvious when one looks at debug > info produced by clang. Such records are normally created by the code like > this: > Instruction->setDebugLoc(llvm::DebugLoc::get(Line, Column, Scope)); > and it appears that Column is always zero. > > Yuri > _______________________________________________ > 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/20140125/75416a50/attachment.html>
On 01/25/2014 01:19, Yaron Keren wrote:> You need to set > > clang::CodeGenOptions.DebugColumnInfo = 1; > > it's not enabled by default.Why this isn't a default? Is there some benefit to keeping it off? Yuri