[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/28058] 300x performance regression in strip
From: |
mail at nh2 dot me |
Subject: |
[Bug binutils/28058] 300x performance regression in strip |
Date: |
Wed, 07 Jul 2021 14:45:13 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=28058
Niklas Hambüchen <mail at nh2 dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Niklas Hambüchen <mail at nh2 dot me> ---
OK, makes sense.
I was hoping that a point release for the past binutils (e.g. 2.35, 2.36
series) could make the fix available to current Linux distributions possible,
as they often do upgrade to bugfix releases, but not major releases in the same
OS release cycle.
I'm not certain what binutils's point release policy is overall -- there seems
to be some of it (e.g. 2.35.1 being released after 2.36), so I wasn't sure
whether such a thing would qualify or not.
Thanks for looking into it!
(Marking as resolved as the fix will be in 2.37.)
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/28058] New: 300x performance regression in strip, mail at nh2 dot me, 2021/07/06
- [Bug binutils/28058] 300x performance regression in strip, mail at nh2 dot me, 2021/07/06
- [Bug binutils/28058] 300x performance regression in strip, mail at nh2 dot me, 2021/07/06
- [Bug binutils/28058] 300x performance regression in strip, mail at nh2 dot me, 2021/07/06
- [Bug binutils/28058] 300x performance regression in strip, nickc at redhat dot com, 2021/07/07
- [Bug binutils/28058] 300x performance regression in strip,
mail at nh2 dot me <=
- [Bug binutils/28058] 300x performance regression in strip, cvs-commit at gcc dot gnu.org, 2021/07/09
- [Bug binutils/28058] 300x performance regression in strip, nickc at redhat dot com, 2021/07/09
- [Bug binutils/28058] 300x performance regression in strip, mail at nh2 dot me, 2021/07/09