[Bug ld/30076] aarch64: stubs can add indirect branch that breaks BTI
https://sourceware.org/bugzilla/show_bug.cgi?id=30076 Alex Coplan changed: What|Removed |Added CC||acoplan at gcc dot gnu.org -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/30248] Internal error in i386_att_operand
https://sourceware.org/bugzilla/show_bug.cgi?id=30248 H.J. Lu changed: What|Removed |Added CC||hjl.tools at gmail dot com --- Comment #1 from H.J. Lu --- This is caused by e87fb6a6d0cdfc0e9c471b7825c20c238c2cf506 is the first bad commit commit e87fb6a6d0cdfc0e9c471b7825c20c238c2cf506 Author: Jan Beulich Date: Wed Oct 5 09:16:24 2022 +0200 x86/gas: support quoted address scale factor in AT&T syntax -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30254] New: iostream crashes with ld linker for windows targets
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 Bug ID: 30254 Summary: iostream crashes with ld linker for windows targets Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- Bug issue 29973 was a mess. So I decided to start a new one and close bug 29973. GCC 13 made several changes to iostream, including making it with an __init_priority__ and changing the definition due to the updated win32 thread model changes. I do not know what breaks it. But any program that uses std::cout/std::cin now will crash when dynamically linked with libstdc++. I have tried LLVM lld. lld does not crash the program, but ld crashes. This breaks nearly all C++ programs on windows since they may use iostream in some places, and the entire program crashes. Maybe ld linker does not correctly deal with __init_priority__ for PE targets. However, I am not an expert on the linker and do not know why. It is very near April, and we will get the latest binutils and GCC 13 published, and GCC 14 will be very soon. This issue needs to be addressed as soon as possible so we do not break Windows programs and GCC bootstrapping when GCC 13 is released. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30254] iostream crashes with ld linker for windows targets
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added Priority|P2 |P1 Severity|normal |critical Target||pe targets -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 cqwrteur changed: What|Removed |Added Resolution|--- |MOVED Status|ASSIGNED|RESOLVED --- Comment #41 from cqwrteur --- move for issue 30254 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/30254] iostream crashes with ld linker for windows targets
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com -- You are receiving this mail because: You are on the CC list for the bug.
Issue 57213 in oss-fuzz: binutils:fuzz_objdump_safe: Timeout in fuzz_objdump_safe
Comment #2 on issue 57213 by amo...@gmail.com: binutils:fuzz_objdump_safe: Timeout in fuzz_objdump_safe https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57213#c2 The only problem here is a relatively short timeout for a large testcase dumping a huge amount of text. -- 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 57072 in oss-fuzz: binutils:fuzz_as: Stack-overflow in symbol_clone_if_forward_ref
Comment #2 on issue 57072 by amo...@gmail.com: binutils:fuzz_as: Stack-overflow in symbol_clone_if_forward_ref https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57072#c2 This is not at all interesting. The testcase generates an enormous expression with a line of what looks to be 136000 inclusive-or operators. Yes, that blows the stack. -- 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.
[Bug gas/27217] aarch64 as Internal error in md_apply_fix at ....../gas/config/tc-aarch64.c:8330.
https://sourceware.org/bugzilla/show_bug.cgi?id=27217 --- Comment #21 from Kinsey Moore --- This has broken again in 2.40, presumably due to the rework that occurred. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/27217] aarch64 as Internal error in md_apply_fix at ....../gas/config/tc-aarch64.c:8330.
https://sourceware.org/bugzilla/show_bug.cgi?id=27217 --- Comment #22 from Kinsey Moore --- To be clear, the "no symbol" error has returned. -- You are receiving this mail because: You are on the CC list for the bug.
Issue 56425 in oss-fuzz: binutils:fuzz_as: Out-of-memory in fuzz_as
Comment #2 on issue 56425 by amo...@gmail.com: binutils:fuzz_as: Out-of-memory in fuzz_as https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56425#c2 Won't fix. This is .rep with a large repeat count. Running out of memory is not an error, just not enough memory. -- 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 56394 in oss-fuzz: binutils:fuzz_dwarf: Out-of-memory in fuzz_dwarf
Comment #2 on issue 56394 by amo...@gmail.com: binutils:fuzz_dwarf: Out-of-memory in fuzz_dwarf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=56394#c2 Won't fix. mmo format object files are compressed, running out of memory is to be expected with any arbitrary limit. -- 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.
