<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 - llvm-objdump prints garbage for absolute symbol values"
href="https://bugs.llvm.org/show_bug.cgi?id=37383">37383</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>llvm-objdump prints garbage for absolute symbol values
</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>Linux
</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-objdump
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>saugustine@google.com
</td>
</tr>
<tr>
<th>CC</th>
<td>echristo@gmail.com, llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>For the simple reproducer below, compare the output of llvm-objdump to the
output of binutils objdump. Both report the same raw bytes for the callq
instruction, but the objdump version has both the correct symbol value and a
nice symbol name.
Steps to reproduce:
$ pwd
~/llvm-svn/build
$ cat t.s
.text
callq foo
$ ./bin/llvm-mc t.s -o t.o -filetype=obj -triple=x86_64-unknown-linux
$ ./bin/ld.lld t.o --defsym foo=0x100
$ ./bin/llvm-objdump -disassemble a.out
...
201000: e8 fb f0 df ff callq -2100997
$ objdump -d a.out
...
201000: e8 fb f0 df ff callq 100 <foo>
Actually, the llvm-objdump version is probably reporting the right value for
one of the many displacement encodings possible for this instruction, but it is
very hard to tell if it is a correct value without digging into binutils
objdump or the isa manual.</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>