search for: lsection_info

...otate location bytes >> that are DWARF expressions, but it's close - I guess those should be >> CHECK-NEXTs, though. In any case, you should be able to check a few lines >> of assembly with the # DW_AT/DW_TAG annotation comments. >> > > I can check for ".quad .Lsection_info+38 #DW_AT_type". > Done in attached patch. > > >> You'd need to add the tu3.cpp from my example if you want to >> demonstrate that the relocation is actually working as intended and >> avoiding the bogus result I showed. >> type-unique-simple-a.ll &...

...WARF expressions, but it's close - I guess those should be >>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>> >>> >>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>> >> Done in attached patch. >> >>> >>> >>>> You'd need to add the tu3.cpp from my example if you want to >>>> demonstrate that the relocation is actually working as intended and >>>> avoidin...

...;t have a nice way to annotate location bytes > that are DWARF expressions, but it's close - I guess those should be > CHECK-NEXTs, though. In any case, you should be able to check a few lines > of assembly with the # DW_AT/DW_TAG annotation comments. > I can check for ".quad .Lsection_info+38 #DW_AT_type". > You'd need to add the tu3.cpp from my example if you want to > demonstrate that the relocation is actually working as intended and > avoiding the bogus result I showed. > type-unique-simple-a.ll > While I agree that having common test cases hel...

...;>> that are DWARF expressions, but it's close - I guess those should be >>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>> of assembly with the # DW_AT/DW_TAG annotation comments. >>> >> >> I can check for ".quad .Lsection_info+38 #DW_AT_type". >> > Done in attached patch. > >> >> >>> You'd need to add the tu3.cpp from my example if you want to >>> demonstrate that the relocation is actually working as intended and >>> avoiding the bogus result I showed. &gt...

...guess those should be >>>>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>> >>>>> >>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>> >>>> Done in attached patch. >>>> >>>>> >>>>> >>>>>> You'd need to add the tu3.cpp from my example if you want to >>>>>> demonstrate that the relocation is a...

...t it's close - I guess those should be >>>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>> >>>> >>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>> >>> Done in attached patch. >>> >>>> >>>> >>>>> You'd need to add the tu3.cpp from my example if you want to >>>>> demonstrate that the relocation is actually working as intended...

...WARF expressions, but it's close - I guess those should be >>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>> >>> >>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>> >> Done in attached patch. >> >>> >>> >>>> You'd need to add the tu3.cpp from my example if you want to >>>> demonstrate that the relocation is actually working as intended and >>>> avoidin...

...;>> that are DWARF expressions, but it's close - I guess those should be >>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>> of assembly with the # DW_AT/DW_TAG annotation comments. >>> >> >> I can check for ".quad .Lsection_info+38 #DW_AT_type". >> > Done in attached patch. > >> >> >>> You'd need to add the tu3.cpp from my example if you want to >>> demonstrate that the relocation is actually working as intended and >>> avoiding the bogus result I showed. &gt...

...be >>>>>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>> >>>>>> >>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>> >>>>> Done in attached patch. >>>>> >>>>>> >>>>>> >>>>>>> You'd need to add the tu3.cpp from my example if you want to >>>>>>> demonstr...

...>>>>>>>> though. In any case, you should be able to check a few lines of assembly >>>>>>>> with the # DW_AT/DW_TAG annotation comments. >>>>>>> >>>>>>> >>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>> >>>>>> Done in attached patch. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> You'd need to add the tu3.cpp from my example if you want to >>&g...

Might be easier if these were on Phabricator, but here are some thoughts: 0001: This patch generally, while separated for legibility, is untested & difficult to discuss in isolation. I may need to refer to the second patch in reviewing this first one. DwarfDebug.cpp: computeSizeAndOffsets: I believe this produces the wrong offset for the 3rd CU and onwards. computeSizeAndOffset

...be >>>>>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>> >>>>>> >>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>> >>>>> Done in attached patch. >>>>> >>>>>> >>>>>> >>>>>>> You'd need to add the tu3.cpp from my example if you want to >>>>>>> demonstr...

...gt; main(int argc, char *argv[]) > { > int a = 11; > int b = 22; > int c = a+b; > return c; > } > > ###################################### > # asm including dwarf debugging info > .file "test.c" > .section .debug_info,"", at progbits > Lsection_info: > .section .debug_abbrev,"", at progbits > Lsection_abbrev: > .section .debug_aranges,"", at progbits > .section .debug_macinfo,"", at progbits > .section .debug_line,"", at progbits > Lsection_line: > .section .debug_loc,"",...

...gt;>>> CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>>> >>>>>>> >>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>>> >>>>>> Done in attached patch. >>>>>> >>>>>>> >>>>>>> >>>>>>>> You'd need to add the tu3.cpp from my example if you want to >>>&...

...CHECK-NEXTs, though. In any case, you should be able to check a few lines >>>>>>>>> of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>>>> >>>>>>>> >>>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>>>> >>>>>>> Done in attached patch. >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> You'd need to add the tu3.cpp from my example if y...

...ugh. In any case, you should be able to check a >>>>>>>>>> few lines of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>>>>> >>>>>>>>> >>>>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>>>>> >>>>>>>> Done in attached patch. >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> You'd need to add the tu3....

...x_func(int, int, int); ======================================================================== Asm -O0 ======================================================================== .file "a.c" .file 1 "/home/marco/clang_issue/a.c" .section .debug_info,"", at progbits .Lsection_info: .section .debug_abbrev,"", at progbits .Lsection_abbrev: .section .debug_aranges,"", at progbits .section .debug_macinfo,"", at progbits .section .debug_line,"", at progbits .Lsection_line: .section .debug_loc,"", at progbits .section .debug_...

All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I

..., you should be able to check a >>>>>>>>>>> few lines of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>>>>>> >>>>>>>>> Done in attached patch. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> You...

..., you should be able to check a >>>>>>>>>>> few lines of assembly with the # DW_AT/DW_TAG annotation comments. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I can check for ".quad .Lsection_info+38 #DW_AT_type". >>>>>>>>>> >>>>>>>>> Done in attached patch. >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> You...