[llvm-bugs] [Bug 43543] New: Handle bitcode files more sensibly

via llvm-bugs llvm-bugs at lists.llvm.org
Thu Oct 3 02:11:59 PDT 2019


https://bugs.llvm.org/show_bug.cgi?id=43543

            Bug ID: 43543
           Summary: Handle bitcode files more sensibly
           Product: tools
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: llvm-readobj
          Assignee: unassignedbugs at nondot.org
          Reporter: jh7370.2008 at my.bristol.ac.uk
                CC: jh7370.2008 at my.bristol.ac.uk, llvm-bugs at lists.llvm.org

If llvm-readobj is passed a bitcode file, an error message of the form "The
file was not recognized as a valid object file" will be produced. This is
reasonable in that llvm-readobj doesn't know about bitcode files. Even if it
did, the only real information it could provide that has a corresponding switch
is stuff about the symbols, and maybe some sort of header information. However,
we've had several users (including myself) not realise they have a bitcode
file, and so get confused when llvm-readobj can't handle their compiler's
output. If the error message said something more like "bitcode files are not
supported", it would save a degree of confusion.

As an alternative stretch goal, we could actually implement some sort of symbol
and file header dumping for bitcode files, but I'm not sure of any use for the
latter, and the former is covered by another tool (llvm-nm).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191003/1f9ea1f0/attachment.html>


More information about the llvm-bugs mailing list