[Bug ld/29998] ld terminated with signal 11 [Segmentation fault] under mingw with LTO
https://sourceware.org/bugzilla/show_bug.cgi?id=29998 --- Comment #24 from Jan Janssen --- The patch seems to work and the EFI binary works as expected. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/29998] ld terminated with signal 11 [Segmentation fault] under mingw with LTO
https://sourceware.org/bugzilla/show_bug.cgi?id=29998 --- Comment #25 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1c66b8a03989b963534689ec0a9cce57e419afd5 commit 1c66b8a03989b963534689ec0a9cce57e419afd5 Author: Nick Clifton Date: Fri Jan 27 11:59:53 2023 + Another fix for EFI generation with LTO enabled. PR 29998 * pe-dll.c (build_filler_bfd): Initialise the next field of the filler input statement, so that it does not break the file chain. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/29998] ld terminated with signal 11 [Segmentation fault] under mingw with LTO
https://sourceware.org/bugzilla/show_bug.cgi?id=29998 Nick Clifton changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #26 from Nick Clifton --- OK, I have applied the patch. I am not 100% convinced that I have fixed it in the best way, but other fixes have the likelyhood of breaking a lot of targets, if I get things wrong. So for now, I am sticking with this patch. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/16177] R_ARM_COPY reloc generated for reference in writable section
https://sourceware.org/bugzilla/show_bug.cgi?id=16177 --- Comment #16 from Nick Clifton --- (In reply to Richard Biener from comment #15) Hi Richard, > It also seems to cause Is there any chance that you could create a reproducer that does not need a compiler or the standard libraries ? I do not have an arm cross compiler (or native compiler) available to me... Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
Issue 55230 in oss-fuzz: binutils:fuzz_as: Null-dereference READ in lbasename
Updates: Labels: -restrict-view-commit Comment #3 on issue 55230 by sheriffbot: binutils:fuzz_as: Null-dereference READ in lbasename https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55230#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 55313 in oss-fuzz: binutils:fuzz_as: Undefined-shift in resolve_expression
Updates: Labels: -restrict-view-commit Comment #3 on issue 55313 by sheriffbot: binutils:fuzz_as: Undefined-shift in resolve_expression https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55313#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 55387 in oss-fuzz: binutils:fuzz_objdump_safe: Null-dereference READ in coff_aarch64_addr32nb_reloc
Updates: Labels: -restrict-view-commit Comment #3 on issue 55387 by sheriffbot: binutils:fuzz_objdump_safe: Null-dereference READ in coff_aarch64_addr32nb_reloc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=55387#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
