[Bug gas/32082] gas arm aarch64: missing mapping symbols $d in the absence of alignment directives

https://sourceware.org/bugzilla/show_bug.cgi?id=32082 Fangrui Song changed: What|Removed |Added Target||arm*-*-* aarch64-*-* -- You are recei

[Bug gas/32082] New: gas arm aarch64: missing mapping symbols $d in the absence of alignment directives

https://sourceware.org/bugzilla/show_bug.cgi?id=32082 Bug ID: 32082 Summary: gas arm aarch64: missing mapping symbols $d in the absence of alignment directives Product: binutils Version: unspecified Status: NEW

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 --- Comment #24 from Fangrui Song --- (In reply to H.J. Lu from comment #6) > It also breaks GCC builds for ARM, AVR, PRU and others. Do you have links to the potentially brittle assembly? In the gcc repo, I checked a few `rg '\.macro' -g '*

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 Fangrui Song changed: What|Removed |Added CC||i at maskray dot me --- Comment #23 fr

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 --- Comment #22 from Maciej W. Rozycki --- (In reply to Michael Matz from comment #20) > I don't have a good solution, I see only hacks (e.g. above: fix _this_ very > instance of '(1) (2)' being pasted, to not be anymore, or alternatively to >

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 Maciej W. Rozycki changed: What|Removed |Added CC||macro at orcam dot me.uk -- You

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 --- Comment #21 from H.J. Lu --- (In reply to Michael Matz from comment #20) > Or: accept the fact that '(1) (2)' is a single macro argument, even if > surprising. I submitted a test for it: https://sourceware.org/pipermail/binutils/2024-Au

[Bug binutils/32072] ./dlltool.c:870:27: error: initializer-string for array of 'char' is too long

https://sourceware.org/bugzilla/show_bug.cgi?id=32072 Alan Modra changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 --- Comment #20 from Michael Matz --- (In reply to Jan Beulich from comment #19) > (In reply to Michael Matz from comment #14) > > The scrubber removes whitespace between tokens of different classes, but > > retains > > whitespace between toke

Re: Questions Regarding Initial Input Seeds Used for Fuzzing Binutils via OSS-Fuzz

Hi Philippe and Nick, Thank you both for the helpful information. Best regards, Federico On Mon, Aug 12, 2024 at 5:46 PM Nick Clifton wrote: > Hi Federico, > > > I have been exploring the Binutils library and its integration with > OSS-Fuzz for fuzzing purposes. > > To be clear: The OSS-Fuzz

[Bug gas/32073] [2.44 Regression] gas failed to build x86-64 Linux kernel

https://sourceware.org/bugzilla/show_bug.cgi?id=32073 --- Comment #19 from Jan Beulich --- (In reply to Michael Matz from comment #14) > The scrubber removes whitespace between tokens of different classes, but > retains > whitespace between token of same class, which sometimes makes it so that >