[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/30725] severe objdump performance regression
From: |
nickc at redhat dot com |
Subject: |
[Bug binutils/30725] severe objdump performance regression |
Date: |
Tue, 15 Aug 2023 13:22:31 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=30725
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at redhat dot com
--- Comment #2 from Nick Clifton <nickc at redhat dot com> ---
Hi Achim,
Is the Cygwin version of objdump build with debuginfod support enabled ?
If so, does adding -wE or --dwarf=do-not-use-debuginfod to the command line
improve the performance times ?
I suspect that the presence of the -l option is the trigger for the slow
down, since this means that the debug information has to be processed in
order to determine the line numbers. Processing DWARF is a slow business
and it has only become slower over successive releases as bug fixing means
that more care has to be taken to handle all the possible intricacies.
Hence - as a workaround, could you omit the use of the -l option ?
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/30725] New: severe objdump performance regression, Stromeko at nexgo dot de, 2023/08/05
- [Bug binutils/30725] severe objdump performance regression, ssbssa at sourceware dot org, 2023/08/05
- [Bug binutils/30725] severe objdump performance regression, sam at gentoo dot org, 2023/08/05
- [Bug binutils/30725] severe objdump performance regression, Stromeko at nexgo dot de, 2023/08/06
- [Bug binutils/30725] severe objdump performance regression,
nickc at redhat dot com <=
- [Bug binutils/30725] severe objdump performance regression, Stromeko at nexgo dot de, 2023/08/17
- [Bug binutils/30725] severe objdump performance regression, Stromeko at nexgo dot de, 2023/08/19