search for: elf2yaml

I'm adding support for elf dynamic symbols in yaml2obj/obj2yaml. I'm seeking opinions about how to model dynamic symbols (and symbols in general) in the yaml structure. Currently, symbols in elf are represented by a top level `Symbols` key, within which symbols are grouped by binding type (Global, Weak, Local). The simplest thing to do would be to mirror this structure to a DynamicSymbols

> I wonder why you want to add the new feature to yaml2obj. Maybe, explaining your motivation would help others understand your problem. Thanks for the cue! I am using yaml2obj to generate stub dynamic libraries. On Wed, Nov 1, 2017 at 11:29 AM, Rui Ueyama <ruiu at google.com> wrote: > I don't have a strong opinion on this. yaml2obj was there when I joined to > the project,

...under lib/ObjectYAML. In general, there seems to be an inconsistency regarding how obj2yaml and yaml2obj tools are structured. The latter has a nice wrapper which calls environment-dependent functions under lib/ObjectYAML, but the former has environment-dependent source files under tools/obj2yaml (elf2yaml.cc, coff2yaml.cc, etc). I wanted to reach out to ask if there is any alternative or get an idea about the amount of refactoring work that is required to make the structure friendlier. bests, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/...

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

...eneral, there seems to be an inconsistency regarding how obj2yaml and >> yaml2obj tools are structured. The latter has a nice wrapper which calls >> environment-dependent functions under lib/ObjectYAML, but the former has >> environment-dependent source files under tools/obj2yaml (elf2yaml.cc, >> coff2yaml.cc, etc). >> >> I wanted to reach out to ask if there is any alternative or get an idea >> about the amount of refactoring work that is required to make the structure >> friendlier. >> >> bests, >> > -------------- next part ------...

...F.h. But this machine information(e_machine) is given to compiler at lib/MC/ELFObjectWriter.cpp. I greped the whole llvm project and found that e_machine was assigned at only two files. One was lib/MC/ELFObjectWriter.cpp(there was an comment said “e_machine=target”) and the other was tools/obj2yaml/elf2yaml.cpp(GDB stopped only at the former one when using x86_64 llvm-cov so I thought it was MC provide this e_machine information to compiler). 2. New error was “Failed to load coverage: No coverage data found” since the compiler cannot get NamesSection(at loadBinaryFormat in CoverageMappingReader...

...F.h. But this machine information(e_machine) is given to compiler at lib/MC/ELFObjectWriter.cpp. I greped the whole llvm project and found that e_machine was assigned at only two files. One was lib/MC/ELFObjectWriter.cpp(there was an comment said “e_machine=target”) and the other was tools/obj2yaml/elf2yaml.cpp(GDB stopped only at the former one when using x86_64 llvm-cov so I thought it was MC provide this e_machine information to compiler). First, I think this reinforces my theory that llvm’s object file reading libraries do not “understand” the architecture you’re working on. Second — and I’m not...

Hi vedant, The program didn't pass the checking "OF->getArch() != Triple(Arch).getArch()" loadBinaryFormat in CoverageMappingReader.cpp and returned an error. It's because "OF->getArch()" returned null and "Triple(Arch).getArch()" returned XXXX(name of my arch). The returned value of " OF->getArch()" is decided by "

...table llvm-symbolizer (without symbols) llvm[2]: Compiling yaml2coff.cpp for Release+Asserts build llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-profdata (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-profdata' llvm[2]: Compiling elf2yaml.cpp for Release+Asserts build llvm[2]: Compiling yaml2elf.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-c-test' llvm[2]: Compiling calc.c for Release+Asserts build llvm[2]: Compiling disassemble.c for Release+Asserts build llvm[2]: Com...