(original) (raw)

I have no experience with debug-ir, but is it possible that the debug-ir pass never sets the debug info version? There should be a named metadata node

!llvm.module.flags = !{..., !123}

!123 = metadata !{i32 1, metadata !"Debug Info Version", i32 2}

in the .ll output. If it is missing, just have a look at the clang sources for an example how to add a module flag.

-- adrian

On Oct 15, 2014, at 8:20 AM, Muneeb Khan <muneeb.khan@it.uu.se> wrote:

Yes, I am using opt and llc from the same version (3.5).
I know that there were issues with debug-ir in 3.4\. I have explored the source tree myself for 3.5 and I know that the pass -debug-ir does kick in with opt.
But I have no clue of what happens with the debug information in (and after) the llc pass.

/Muneeb

On 15 Oct 2014, at 17:14, David Blaikie <dblaikie@gmail.com> wrote:

On Wed, Oct 15, 2014 at 7:08 AM, Muneeb Khan <muneeb.khan@it.uu.se> wrote:
Hi,
I am using the -debug-ir pass in LLVM-3.5 opt tool to map binary information back to the IR instead of the source files.
I use the opt tool to generate a .ll file. But when I run the llc tool on it to generate an assembly (or object) file, it gives me the following warning

warning: ignoring debug info with an invalid version (0) in

Are you using opt and llc from the same LLVM version? (mixing and matching could produce this problem)

Or possibly debug-ir was never updated to produce the dubug info version - Adrian?

How can I use the debug-ir functionality to achieve a mapping from the binary to the IR?
Thanks!

Muneeb Khan
PhD student
Department of Information Technology,
Uppsala University,
Sweden
Tel: +46 18 - 471 1049

_______________________________________________

LLVM Developers mailing list

LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu

http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Muneeb Khan
PhD student
Department of Information Technology,
Uppsala University,
Sweden
Tel: +46 18 - 471 1049