https://sourceware.org/bugzilla/show_bug.cgi?id=24993
Jim Wilson <wilson at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Last reconfirmed| |2019-09-12 Resolution|INVALID |--- Ever confirmed|0 |1 Severity|normal |enhancement --- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> --- I'm getting compiler bug reports from people using objdump -D, seeing invalid code in the data section, and then assuming the compiler must be broken and filing a bug report. This is causing trouble for me. I really need people to stop using objdump -D unless they have a specific need for it. It is important to get the message out to the RISC-V user community that using objdump -D is wrong, and they should be using objdump -d instead. Unfortunately, I don't know why so many people are using objdump -D instead of objdump -d. I suspect some badly written documentation somewhere. I agree that the objdump -D output could be improved. I'd be OK with this as an enhancement request, but I'm not considering it a bug, as you shouldn't be using objdump -D in the first place. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils