search for: diestring

...n the BumpPtrAllocator, also take up a huge amount of memory (around 4%): Graph Category Persistent Bytes # Persistent # Transient Total Bytes # Total Transient/Total Bytes 0 llvm::DIEInteger 19.91 MB 652389 0 19.91 MB 652389 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 0 llvm::DIEString 13.83 MB 302181 0 13.83 MB 302181 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 0 llvm::DIEEntry 10.91 MB 357506 0 10.91 MB 357506 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 0 llvm::DIEDelta 10.03 MB 328542 0 10.03 MB 328542 <XRRatioObject: 0x608025658ea0> %0.00, %0.00...

...s we will be able to use when generating DWARF info. Adrian Prantl attempted to help me get things working over here and we kept running into roadblocks. > > It'd be great to have more detail about the roadblocks you hit to better understand how bad/what the issues are. A few blocks: - DIEString doesn't support DW_FORM_string. DW_FORM_string support might have been pulled so that we never emit it from clang, but we would want to have a unit test that covers being able to read an inlined C string from a DIE. Support won't be that hard to add, but we might not want it so that people...

...empted to help me get things working over here and we kept running into >> roadblocks. >>> >>> It'd be great to have more detail about the roadblocks you hit to better >> understand how bad/what the issues are. >> >> A few blocks: >> >> - DIEString doesn't support DW_FORM_string. DW_FORM_string support might >> have been pulled so that we never emit it from clang, but we would want to >> have a unit test that covers being able to read an inlined C string from a >> DIE. Support won't be that hard to add, but we might...

...ake up a huge amount of memory (around 4%): >> >> Graph Category Persistent Bytes # Persistent # Transient Total Bytes # Total Transient/Total Bytes >> 0 llvm::DIEInteger 19.91 MB 652389 0 19.91 MB 652389 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 >> 0 llvm::DIEString 13.83 MB 302181 0 13.83 MB 302181 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 >> 0 llvm::DIEEntry 10.91 MB 357506 0 10.91 MB 357506 <XRRatioObject: 0x608025658ea0> %0.00, %0.00 >> 0 llvm::DIEDelta 10.03 MB 328542 0 10.03 MB 328542 <XRRatioObject: 0x608025658ea0>...

...and we kept running > into > >> roadblocks. > >>> > >>> It'd be great to have more detail about the roadblocks you hit to > better > >> understand how bad/what the issues are. > >> > >> A few blocks: > >> > >> - DIEString doesn't support DW_FORM_string. DW_FORM_string support might > >> have been pulled so that we never emit it from clang, but we would want > to > >> have a unit test that covers being able to read an inlined C string > from a > >> DIE. Support won't be that h...

I have recently been modifying the DWARF parser and have more patches planned and I want to be able to add unit tests that test the internal llvm DWARF APIs to ensure they continue to work and also validate the changes that I am making. There are not many DWARF unit tests other than very simple ones that test DWARF forms currently. I would like to expand this to include many more tests. I had