<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Handle bitcode files more sensibly"
href="https://bugs.llvm.org/show_bug.cgi?id=43543">43543</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Handle bitcode files more sensibly
</td>
</tr>
<tr>
<th>Product</th>
<td>tools
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>llvm-readobj
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jh7370.2008@my.bristol.ac.uk
</td>
</tr>
<tr>
<th>CC</th>
<td>jh7370.2008@my.bristol.ac.uk, llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>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).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>