Planned binutils-2.46.1 release

[Sam James]

Alan Modra <amodra@gmail.com> writes:

> On Tue, May 12, 2026 at 07:37:16PM +0100, Sam James wrote:
>> Sam James <sam@gentoo.org> writes:
>> 
>> > Hi all,
>> >
>> > I plan to make a point release for binutils-2.46 in a few days,
>> > motivated by the C23/glibc-2.43 fixes for const correctness, as the 2.46
>> > release fails to build w/ -Werror enabled by default [0].
>> >
>> > Please look to see if any other fixes should be backported to
>> > binutils-2_46-branch.
>> >
>> > Right now, there are fixes there for:
>> > * PR34028
>> > * PR34088
>> > * PR34125
>> >
>> > I don't think there's anything else which needs to go in but I may well
>> > have missed something. Thanks in advance.
>> 
>> Maybe this one, given it makes the migration from v2->v3 much nicer:
>> 
>> commit 7c80233f4d47c2508d8984bdcfc644b9a6e7bf9a
>> Author:     Alan Modra <amodra@gmail.com>
>> AuthorDate: Fri Mar 13 08:55:04 2026 +1030
>> Commit:     Alan Modra <amodra@gmail.com>
>> CommitDate: Fri Mar 13 08:55:04 2026 +1030
>> 
>>     check sframe version in _bfd_elf_parse_sframe
>>     ...
>
> Fair enough.

Thanks for handling it Alan, and sorry for taking a while.

>
>> It would need a slight tweak to apply cleanly or we just include
>> 9eae5ed721cd117c492fcb4516724bf093d4ea2d and
>> 3949fb481a6739dc1f4dc5fad09d7646c90af3d2 as well.
>
> As a general principle I don't recommend backporting fuzzing fixes or
> "not freed before exit" type memory leak fixes, unless backporting
> them makes it a lot easier to backport some other wanted fix.

Ack.

>
>> Anyway, any opinions Alan or Indu?
>> 
>> >
>> > [0] https://inbox.sourceware.org/binutils/c4e611d0-2ef2-4495-8623-7ec82df3f101@gmail.com/
>> >
>> > sam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 418 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20260609/7b7c6e8d/attachment.sig>