search for: readobj

Hi all, A broad goal of many of the LLVM binary tools, such as llvm-objcopy and llvm-objdump is to provide an alternative to the GNU equivalent, and as such, these tools have been developed to be command-line compatible. One tool where this hasn’t been the case up to now is llvm-readobj (aka llvm-readelf). There was some discussion in https://reviews.llvm.org/D33872 about the purpose of llvm-readobj, so I’d like to ask the community's opinion. What is the purpose of llvm-readobj? Is it purely intended as an aid to testing? Should it be aiming to be GNU compatible, like most o...

...A broad goal of many of the LLVM binary tools, such as llvm-objcopy and >> llvm-objdump is to provide an alternative to the GNU equivalent, and as >> such, these tools have been developed to be command-line compatible. One >> tool where this hasn’t been the case up to now is llvm-readobj (aka >> llvm-readelf). >> > I don't want to digress too much, but llvm-objdump isn't compatible > either. For instance, "-df" is an llvm-objdump flag that accepts a list of > functions to disassemble, but objdump accepts "-df" as a merged form of &qu...

Hi All, I see that llvm-readobj displays information similar to GNU readelf does except DWARF data. I also see llvm-dwarfdump dumps all DWARF data in user readable format. Is there a plan for readobj to incorporate similar options? This will make readobj more feature complete for reading objects similar to readelf. If this is...

...ot; integer types, instead of the stdint.h typedefs? On 09/20/2017 11:03 PM, Marek Sokolowski via llvm-commits wrote: > Author: mnbvmar > Date: Wed Sep 20 14:03:37 2017 > New Revision: 313816 > > URL: http://llvm.org/viewvc/llvm-project?rev=313816&view=rev > Log: > [llvm-readobj] Fix 'Teach readobj to dump .res files'. > > Fix-up for r313790. Some buildbots couldn't convert size_t to > uint{}_t; do it manually. > > Modified: > llvm/trunk/tools/llvm-readobj/WindowsResourceDumper.cpp > > Modified: llvm/trunk/tools/llvm-readobj/Wind...

Hi all, llvm-readelf is an alias for llvm-readobj which aims for GNU compatibility and is likely the tool that most people migrating to the LLVM binutils will adopt instead of llvm-readobj. Because it is just an alias, it has inherited the functionality provided by llvm-readobj, including for non-ELF targets, with Mach-O and COFF-specific switches...

...put from the LLVM Binutils. Before I actually start advertising this as an open project, I wanted to ask a few questions: 1. Are people still interested in this? If so, what is the typical use case you’d use the result of this project for? Why would this be better than the existing llvm-readobj output (if applicable)? 2. Which tool(s) and feature(s) would you most want this for? I personally think this should just be another output style for llvm-readobj. Does anybody have any different opinion there? 3. Is there any additional tooling in relation to this project that you t...

...ilities use cl::ParseCommandLineOptions() (include/Support/CommandLine.h) to parse command line options. The cl library accepts both -long-option and --long-option forms, with the single dash form (-long-option) being more popular. We also have many binary utilities (llvm-objcopy llvm-objdump llvm-readobj llvm-size ...) whose names reflect what they imitate. For compatibility with GNU binutils (and some Unix utilities transitively), these utilities accept many short options. People who use llvm utilities as replacement of GNU binutils may use the grouped option syntax (POSIX Utility Conventions), e....

Hello LLVM-World, I have a question about dumping debug information. 1.) I have compiled an object file with visual studio and debug information. Then I used "llvm-readobj -codeview" and dumped the debug information into a file. This is working great 2.) I used clang-cl for the same task and finally dumped it again with "llvm-readobj". Worked great too. 3.) Then I used clang-cl to generate a .bc file - but now I'm not able to use "llvm-re...

...have to run the file through llc to generate an object file to generate actual CodeView or DWARF. On Wed, Jan 17, 2018 at 5:09 AM, 陳韋任 via llvm-dev <llvm-dev at lists.llvm.org> wrote: > 3.) Then I used clang-cl to generate a .bc file - but now I'm not able to >> use "llvm-readobj" anymore. Is there any tool available which can dump this >> debug information too? >> > > ​.bc is LLVM bitcode [1], not the usual object file. `llvm-readobj` should > works only on the latter. > > ​[1] https://llvm.org/docs/BitCodeFormat.html > > -- > Wei-R...

For binutil compatibility, and in general for any new tools, this sounds reasonable to me. But I'd worry that things like llvm-readobj have existed for a long time and people are used to flags like "-sections", and it may be complicated to change that now. (I guess this RFC is a check to see if this is true for anyone on the mailing list). What happens if you make this change and someone does use "-sections" -...

...l LLVM utilities? No. Only drop --long-option for GNU binutils replacements (people sometimes call them LLVM binary utilities): llvm-objcopy (D60439), llvm-ar, llvm-size, llvm-nm, etc. llvm-objdump (not sure what to do with mach-o specific dump options), llvm-readelf (not sure what to do with llvm-readobj) On Sat, Apr 20, 2019 at 2:13 AM Reid Kleckner <rnk at google.com> wrote: > Are you proposing to make this the new style across all LLVM utilities? > That seems needlessly disruptive. There are plenty of scripts that call > `opt` and `llc` directly with single dash long options, re...

...h previous versions of LLVM, we're better off doing it > now, rather than leaving it a long time. The longer it gets left, the more > users, and therefore the more likely somebody has come to rely on it in a > non-trivial-to-fix way. > > If we are particularly concerned with llvm-readobj, we could (if it is > practical) try handling it differently to llvm-readelf. An approach as > suggested by Michael Spencer at the BoF could be to migrate away from using > cl::opt and follow the same route as llvm-objcopy. That would allow us to > have different option sets for the two...

With the correct list this time. On Wed, Sep 9, 2015 at 6:59 PM, Davide Italiano <davide at freebsd.org> wrote: > Hi, > in the last month I spent some time implementing the missing MachO > specific features in llvm-readobj, and converting all the remaining > tests that used macho-dump to the new format. > llvm-readobj should have all the functionality that macho-dump had. If > there's something missing, please open a bug and assign to me, I'll > try to do my best to fill the gap. > > That sa...

Thank you for your reply. When I'm running "llvm-readobj" on an .obj file I get a result like shown in my attachment. This is very easy to read. I don't know if this is the codeview format. I would like to get this kind of debug information form a .bc file too, because I JIT them and wanted to try to build a debugger. With the file from &quo...

Hi all, I have implemented AsmParser, CodeEmitter, and ELF object writing. AsmParser and CodeEmitter are tested and working fine, but I would like to see ELF objects build out of a parsed asm file. Is that possible? I tried this commands, but it didn't work corrctly: *llvm-mc -filetype=obj -arch=test file.s -o=a.o* and I think after an obj file is built, I should use this command but I am

...32/debug/pe-format#debug-directory-image-only> recently came up during a code review<https://reviews.llvm.org/D70606#1873185>. Currently, its COFF syntax<http://llvm.org/docs/yaml2obj.html#coff-syntax> allows for specifying section data, but not debug directories, that's why llvm-readobj tests which depend on debug directory contents use pre-built executable images instead of yaml2obj. It is possible to extend the tool, but first I would be interested in gathering feedback on usability of this, especially on potential uses of this change. It looks like porting llvm-readobj tests f...

> > 3.) Then I used clang-cl to generate a .bc file - but now I'm not able to > use "llvm-readobj" anymore. Is there any tool available which can dump this > debug information too? > ​.bc is LLVM bitcode [1], not the usual object file. `llvm-readobj` should works only on the latter. ​[1] https://llvm.org/docs/BitCodeFormat.html -- Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nc...

...mp; !isHidden(); } Alternatively I've misunderstood the full meaning of SF_Hidden and SF_Exported. I always just read them as "will this symbol appear in the symbol table for a linked DSO". Under that reading, a non-hidden, non-exported symbol doesn't make sense. > I believe readobj already dumps this sort of information out, albeit in object file specific ways. Ok. I eventually need something that shows the generic flag's value, but the output format of the tool can be object specific. For other properties (e.g. "weak") llvm-objdump and llvm-nm suffice, since t...

...l relevant object files. High Level Design ================= - LLVM: We provide machinery for individual passes to dump arbitrary messages into a special ELF section in a compressed manner. - Linker: We simply concatenate the contents of the special ELF section. No change is needed. - llvm-readobj: We add an option to retrieve the contents of the special ELF section. Detailed Design =============== DumpAccumulator analysis pass ----------------------------- We create a new analysis pass called DumpAccumulator. We add the analysis pass right at the beginning of the pass pipeline. The n...

...K 'ba' /home/csabaraduly/wk/LLVM-git/__build_release_99/test/tools/llvm-objcopy/ELF/Output/regex.test.tmp /home/csabaraduly/wk/LLVM-git/__build_release_99/test/tools/llvm-objcopy/ELF/Output/regex.test.tmp2 : 'RUN: at line 5'; /home/csabaraduly/wk/LLVM-git/__build_release_99/bin/llvm-readobj --symbols /home/csabaraduly/wk/LLVM-git/__build_release_99/test/tools/llvm-objcopy/ELF/Output/regex.test.tmp2 | /home/csabaraduly/wk/LLVM-git/__build_release_99/bin/FileCheck /home/csabaraduly/wk/LLVM-git/llvm/test/tools/llvm-objcopy/ELF/regex.test --check-prefix=REGEX1 : 'RUN: at line 8';...