search for: cfi_assembl

...a lot of things like actual DWARF encoding. Err, .cfi_ and used because the encoding is tricky to get right, and assemblers are better at optimizing it. However, i'll point out that breakpad also has a CFI assembler (http://code.google.com/p/google-breakpad/source/browse/trunk/src/common/dwarf/cfi_assembler.cc) > > The long-term solution for DWARF would be to enhance lib/DebugInfo to > the point where it can handle all interesting DWARF sections. But this > is a lofty goal, since DWARF parsing is notoriously hard and this > would require a large investment of time and effort. ????? H...

...ual DWARF encoding. > > Err, .cfi_ and used because the encoding is tricky to get right, and > assemblers are better at optimizing it. > However, i'll point out that breakpad also has a CFI assembler > (http://code.google.com/p/google-breakpad/source/browse/trunk/src/common/dwarf/cfi_assembler.cc) > >> >> The long-term solution for DWARF would be to enhance lib/DebugInfo to >> the point where it can handle all interesting DWARF sections. But this >> is a lofty goal, since DWARF parsing is notoriously hard and this >> would require a large investment of...

Hi All, While working on some recent patches for x32 support, I ran into an unpleasant limitation the LLVM eco-system has with testing DWARF emission. We currently have several approaches, neither of which is great: 1. llvm-dwarfdump: the best approach when it works. But unfortunately lib/DebugInfo supports only a (small) subset of DWARF. Tricky sections like debug_frame aren't supported. 2.