[LLVMbugs] [Bug 14501] New: Debug info for constants have no line information

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=14501

             Bug #: 14501
           Summary: Debug info for constants have no line information
           Product: clang
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Keywords: googler
          Severity: enhancement
          Priority: P
         Component: C++
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: dblaikie at gmail.com
                CC: dan433584 at gmail.com, dgregor at apple.com,
                    echristo at gmail.com, llvmbugs at cs.uiuc.edu
            Blocks: 14330
    Classification: Unclassified


GDB 7.5 test suite's gdb.pytho/python.exp tests a fairly specific case:

int func() {
  func2();
  return 0;
}

break at line 2 (the call to func2)
step into func2
go up (gdb "up" command) one frame
print the line of the pc ("python print
gdb.find_pc_line(gdb.selected_frame().pc()).line")

The instruction following the func2 call is assigned to the same line as
"return 0" in GCC's debug info. In Clang's debug info this line has no debug
info of its own, so it is on the same line as the prior instruction (the call
to func2).

Subtle/may or may not be an important issue, but this might be as good a place
as any to start thinking about/tracking how Clang's fast isel constant emission
may be adversely impacting debugging.

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.