https://sourceware.org/bugzilla/show_bug.cgi?id=30063
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
(In reply to Stas Sergeev from comment #2)
> May I guess that the fix went to the older branches as a
> back-port, but wasn't initially in them?
Possibly - or ... it could be that it was never a bug in the upstream
binutils sources, but rather a bug that was introduced by the patches
that distribution maintainers apply on top of the stock sources.
> Do you know in what version it initially went in, not as a back-port?
Sorry no. I checked as far back as 2.37, but I do not have earlier
releases to hand. (I could get them, but it would be a hassle).
> Or maybe you know the exact commit that I should ask the distro
> to apply?
Given that, for example, the bug is not present when running a linker
built from the upstream 2.39 binutils sources, but it is present when
running the Fedora rawhide linker (which is 2.39 + local patches), I
would say that it is unlikely that a commit is missing from the sources.
> If you don't have such info, then feel free to close.
> This bug is not urgent (its only about a bad diagnostic), so if
> there is no concrete patch to back-port, then I'll live without
> it quite well. :)
OK, well I am going to close this PR, but do feel free to raise it
with whichever distribution you use.
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
