[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/19640] New: Objdump version 2.25.1 display bug -> 00 rows
From: |
jdetter at wisc dot edu |
Subject: |
[Bug binutils/19640] New: Objdump version 2.25.1 display bug -> 00 rows |
Date: |
Mon, 15 Feb 2016 23:20:59 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=19640
Bug ID: 19640
Summary: Objdump version 2.25.1 display bug -> 00 rows
Product: binutils
Version: 2.25
Status: NEW
Severity: minor
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: jdetter at wisc dot edu
Target Milestone: ---
Created attachment 8989
--> https://sourceware.org/bugzilla/attachment.cgi?id=8989&action=edit
Output of running objdump -D ./binary
I'm getting some weird output bugs with using objdump with avx-512
instructions. I will get random rows of all 00's. It's not blocking me on my
work, but I'm wondering if there is a way to resolve this. I have attached the
example output, the bug appears on the following lines:
703, 705, 707, 709, 711, 713, 715, 717,
915, 917, 919, 921,
1006, 1008, 1010, 1012,
1097, 1099, 1101, 1103, 1105, 1107, 1109, 1111, 1113, 1115, 1117
1119, 1121, 1123, 1125, 1127
The binary used to produce the output can be obtained here:
http://cs.wisc.edu/~detter/binary
Here is my version information:
address@hidden (47)$ objdump --version
GNU objdump (GNU Binutils) 2.25.1
Copyright (C) 2014 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) any later version.
This program has absolutely no warranty.
The command used to produce the given sample output:
objdump -D ./binary
--
You are receiving this mail because:
You are on the CC list for the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug binutils/19640] New: Objdump version 2.25.1 display bug -> 00 rows,
jdetter at wisc dot edu <=