search for: exprloc

...an be quite compact)) But one place that DWARFv5 misses to reduce relocations further is direct addresses from debug_info, such as DW_AT_low_pc. For a while I've wondered if we could use an extension form for addr+offset, and I prototyped this without an extension attribute, but instead using exprloc. This has slightly higher overhead to express the... expression. (it's 9 bytes in total, could be as few as 5 with a custom form) But I had another idea that's more instantly deployable: Why not use DW_AT_ranges even when the range is contiguous? That way the low_pc that previously couldn&...

...ce that DWARFv5 misses to reduce relocations further is > direct addresses from debug_info, such as DW_AT_low_pc. > > > > For a while I've wondered if we could use an extension form for > addr+offset, and I prototyped this without an extension attribute, but > instead using exprloc. This has slightly higher overhead to express the... > expression. (it's 9 bytes in total, could be as few as 5 with a custom > form) > > > > But I had another idea that's more instantly deployable: Why not use > DW_AT_ranges even when the range is contiguous? That way...

...reduce relocations further is > > direct addresses from debug_info, such as DW_AT_low_pc. > > > > > > For a while I've wondered if we could use an extension form for > > addr+offset, and I prototyped this without an extension attribute, but > > instead using exprloc. This has slightly higher overhead to express the... > > expression. (it's 9 bytes in total, could be as few as 5 with a custom > > form) > > > > > > But I had another idea that's more instantly deployable: Why not use > > DW_AT_ranges even when the range...

...addresses from debug_info, such as DW_AT_low_pc. >>>> > > >>>> > > For a while I've wondered if we could use an extension form for >>>> > addr+offset, and I prototyped this without an extension attribute, but >>>> > instead using exprloc. This has slightly higher overhead to express the... >>>> > expression. (it's 9 bytes in total, could be as few as 5 with a custom >>>> > form) >>>> > > >>>> > > But I had another idea that's more instantly deployable: Why no...

...3/llvm/lib/Target/ARM/AsmParser/ARMAsmParser.cpp: In member function ‘bool {anonymous}::ARMAsmParser::tryParseRegisterWithWriteBack(llvm::SmallVectorImpl<llvm::MCParsedAsmOperand*>&)’: /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/AsmParser/ARMAsmParser.cpp:1979:11: warning: variable ‘ExprLoc’ set but not used [-Wunused-but-set-variable] /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/Disassembler/ARMDisassembler.cpp: In function ‘DecodeStatus DecodeCopMemInstruction(llvm::MCInst&, unsigned int, uint64_t, const void*)’: /home/greened/src/llvm-30-rc3/llvm/lib/Target/ARM/Disassembl...

Hi, [ I think I put the most important contributors to the DebugInfo stuff in Cc:. Is there anyone else that I am missing? ] Just a short notice that I am currently working on making llvm-dwarfdump more developer friendly. There are quite a few features in Darwin’s dwarfdump that we find quite useful and that we would like to contribute to llvm-dwarfdump. I have started by augmenting the

On 7 November 2011 22:00, Bill Wendling <wendling at apple.com> wrote: > We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: > >        http://llvm.org/pre-releases/3.0/rc3/ > > for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your

Good day, LLVMers! We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: http://llvm.org/pre-releases/3.0/rc3/ for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your projects, and let us know if you find any regressions from the 2.9 release. Please keep