[LLVMbugs] [Bug 14660] New: debug info loop condition checks should be associated with the loop header, not the end of the scope
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Wed Dec 19 14:56:09 PST 2012
http://llvm.org/bugs/show_bug.cgi?id=14660
Bug #: 14660
Summary: debug info loop condition checks should be associated
with the loop header, not the end of the scope
Product: clang
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: googler
Severity: enhancement
Priority: P
Component: C++
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: dblaikie at gmail.com
CC: dgregor at apple.com, echristo at gmail.com,
llvmbugs at cs.uiuc.edu
Blocks: 14330
Classification: Unclassified
given:
while (*myp > 0) {
(*myp)++;
}
Clang produces a line table that includes the condition test on the 3rd line
(the closing '}') leading to the jump back to the start of the loop.
GCC produces a line table that associates that condition test with the first
line of the code, not the 3rd.
GCC's behavior makes more sense to me as I expect the condition test to be
matched to the line on which the user wrote the condition.
Causes failures in gdb.threads/schedlock.exp
--
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.
More information about the llvm-bugs
mailing list