search for: pr36420

...line 26. (gdb) c Continuing. Breakpoint 2, myfunction (arg=0) at explicit.c:27 27 ++j; /\* top location */ (gdb) However, LLVM does not generate debug information for labels. So, the feature could not work for binaries generated by clang. I also found that the problem is reported in PR35526 and PR36420. I propose an implementation plan to support debug information for labels. Following are the steps I propose to implement the feature. 1. Define debug metadata and intrinsic functions for labels. First of all, we need to record debug information in LLVM IR. In LLVM IR, LLVM uses metadata and int...

...Breakpoint 2, myfunction (arg=0) at explicit.c:27 > 27 ++j; /\* top location */ > (gdb) > > However, LLVM does not generate debug information for labels. So, the > feature could not work for binaries generated by clang. I also found > that the problem is reported in PR35526 and PR36420. I propose an > implementation plan to support debug information for labels. > > Following are the steps I propose to implement the feature. > > 1. Define debug metadata and intrinsic functions for labels. > > First of all, we need to record debug information in LLVM IR. In LLV...

...Breakpoint 2, myfunction (arg=0) at explicit.c:27 > 27 ++j; /\* top location */ > (gdb) > > However, LLVM does not generate debug information for labels. So, the > feature could not work for binaries generated by clang. I also found > that the problem is reported in PR35526 and PR36420. I propose an > implementation plan to support debug information for labels. > > Following are the steps I propose to implement the feature. > > 1. Define debug metadata and intrinsic functions for labels. > > First of all, we need to record debug information in LLVM IR. In LLV...

...Breakpoint 2, myfunction (arg=0) at explicit.c:27 > 27 ++j; /\* top location */ > (gdb) > > However, LLVM does not generate debug information for labels. So, the > feature could not work for binaries generated by clang. I also found > that the problem is reported in PR35526 and PR36420. I propose an > implementation plan to support debug information for labels. Thank you for working on this! I think it would be good to support labels better. IIRC it currently only generates them from assembler sources in place of a DW_TAG_subprogram. > Following are the steps I propose t...

...n (arg=0) at explicit.c:27 >> 27 ++j; /\* top location */ >> (gdb) >> >> However, LLVM does not generate debug information for labels. So, the >> feature could not work for binaries generated by clang. I also found >> that the problem is reported in PR35526 and PR36420. I propose an >> implementation plan to support debug information for labels. > > Thank you for working on this! I think it would be good to support labels better. IIRC it currently only generates them from assembler sources in place of a DW_TAG_subprogram. > > >> Following...