search for: ehframesect

...ned or duplicated symbols are more informative and easy to read. Below are examples of the current error messages (note that characters in red are actually red on terminal): *Undefined symbols* /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol 'lld::elf::EhFrameSection<llvm ::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*)' *Conflicting symbols* /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:38: duplicate symbol 'lld::elf::MipsGotSection::addEntry(lld::elf::SymbolBody&,...

...wrote: > Put it all together, the following error messages should work for > everybody. I'll create a patch to make this change and send it for > review. Thank you guys for the inputs! > > > Undefined symbol error: > > bin/ld.lld: error: undefined symbol: > lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, > true> > *>>> defined at* Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) > *>>>* Writer.cpp.o in archive lib/liblldELF.a The wording of this one is mildly self contradictory. Undefined...

...ead, but I just want to say that the new format looks awesome! Thanks, Rafael On 29 March 2017 at 15:18, Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> wrote: > My bad. I intended this. > > Undefined symbol error: > > bin/ld.lld: error: undefined symbol: > lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, > true> >>>> Referenced by Writer.cpp:207 (/ssd/llvm-project/lld/ELF/Writer.cpp:207) >>>> Writer.cpp.o in archive lib/liblldELF.a > > > Duplicate symbol error: > > bin/ld.lld: err...

...#39;s output into `less` or `tee`) are still a bit easier to parse in > the presence of wrapped lines. > Makes sense. I tried a few different formats based on suggestions from Mehdi, Hans and you, and come up with this one. What do you think? bin/ld.lld: *error:* undefined symbol: lld::elf::EhFrameSection<llvm::object::ELFType<(llvm::support::endianness)0, true> >::addSection(lld::elf::InputSectionBase*) *>>> referenced by* /home/buildslave/buildslave/clang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207 *>>>* lib/liblldELF.a(Writer.cpp.o) bin/l...

...o parse in >>> the presence of wrapped lines. >>> >> >> Makes sense. I tried a few different formats based on suggestions from >> Mehdi, Hans and you, and come up with this one. What do you think? >> >> bin/ld.lld: *error:* undefined symbol: lld::elf::EhFrameSection<llvm: >> :object::ELFType<(llvm::support::endianness)0, true> >> >::addSection(lld::elf::InputSectionBase*) >> *>>> referenced by* /home/buildslave/buildslave/cl >> ang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207 >> *>>>*...

...e`) are still a bit easier to parse in >> the presence of wrapped lines. >> > > Makes sense. I tried a few different formats based on suggestions from > Mehdi, Hans and you, and come up with this one. What do you think? > > bin/ld.lld: *error:* undefined symbol: lld::elf::EhFrameSection<llvm: > :object::ELFType<(llvm::support::endianness)0, true> > >::addSection(lld::elf::InputSectionBase*) > *>>> referenced by* /home/buildslave/buildslave/cl > ang-cmake-aarch64-39vma/llvm/tools/lld/ELF/Writer.cpp:207 > *>>>* lib/liblld...

Hi all, I am experimenting with extending ELF. I want to add a custom ELF section, something similar to a 'SyntheticSection'. However, I'm not able to find documentation / doxygen for LLD code. Are there any existing examples of adding custom ELF sections at link time in LLVM framework? Is it possible? Any pointers? Thanks in advance!Cheers! -------------- next part -------------- An

Hi all, At the recent LLVM developers' meeting, I presented a lightning talk on an approach to reduce the amount of dead debug data left in an executable following operations such as --gc-sections and duplicate COMDAT removal. In that presentation, I presented some figures based on linking a game that had been built by our downstream clang port and fragmented using the described approach.

...choice. That being said, I think it's format is not too complex, so >>> similarly the parser isn't too complex. You can see LLD's ELF >>> implementation in ELF/EhFrame.cpp, how it is used in ELF/InputSection.cpp >>> (see the bits to do with EhInputSection) and EhFrameSection in >>> ELF/SyntheticSections.h (plus various usages of these two throughout the >>> LLD code). I think the key to any structural changes in the DWARF format to >>> make them more amenable to link-time parsing is being able to read a >>> minimal amount without...