search for: dw_at_start_scope

...DW_AT_name ("Local") DW_AT_decl_file ("MainScope.c") DW_AT_decl_line (7) DW_AT_type (0x0000008a "int") ---------------------------------------------- The DWARF specification provides the DW_AT_start_scope attribute to deal with this issue (Sec 3.9 Declarations with Reduced Scope DWARFv5). This attribute aims at limiting the scope of variables within the lexical scope in which it is defined to from where it has been declared/ defined. In order to fix this issue, we want to modify llvm so that DW_A...

Hi Sourabh, Thanks for raising this issue. To answer your question, (afaik) there isn’t anyone working on DW_AT_start_scope support in tree. We’re looking for a solution to this problem for Swift debugging, where it's important not to make a debug location for a variable available until its (guaranteed) initialization is complete. If at all possible, I’d /much/ rather we use the existing location list machinery to...

In the version of LLVM I'm using (Apple tag 2352.1), it seems that the DWARF emitter cannot produce DWARF location lists to outline when user variables live and where. Instead it uses a crutch of DW_AT_start_scope to specify each solitary location where an assignment to a user variable does occur. This is unsatisfactory for machines that put user variables in registers because it doesn't specify when a register is used for some other purpose, leaving the debugger no clue about when a user's variable...

Hi Reid, Thanks for taking this on, I'm very pleased to see improvements related to debug info for optimized code. (You can cc me on code reviews, although I'm sure a lot of the patches will be in areas I am not very familiar with.) While I have a really good handle on the DWARF standard, and have done a bunch of work with the type stuff, my understanding of IR mechanics is pretty naïve,

...in location 8(%ebp). If I use a different compiler (PGI C compiler): pgcc -tp=k8-32 -O2 -g -c argpass.c I've got following DWARF information for 'c' parameter: ... <2><68>: Abbrev Number: 3 (DW_TAG_formal_parameter) <69> DW_AT_name : c <6b> DW_AT_start_scope : 0x3 <6f> DW_AT_type : <0x77> <73> DW_AT_location : 2 byte block: 91 8 (DW_OP_fbreg: 8) ... and value of 'c' can be inspected in GDB. So my questions are: Is there a way to enforce clang to generate DWARF information similar to pgcc ? For the...