https://sourceware.org/bugzilla/show_bug.cgi?id=33720
--- Comment #5 from Thomas Debesse <dev at illwieckz dot net> --- Some additional information that can be useful: I first reproduced the bug on 2025-04-09. At the time I was attempting to build with GCC a code that was traditionally built with Clang. So at first it was assumed the code was only written for some Clang toolchain specificities and was not purposed to be built with GCC. Then later when investigating more deeply the issue, we found a way to workaround the problem and make the code buildable on GCC so this looked like a GCC limitation. Then it was noticed that some older GCC versions could build it. We also found that the code was purposed to also be buildable with GCC in general. So we knew it was a bug and actually a regression, but at first it looked like to be a bug in GCC itself. Then after much investigation it appears the bug may be in binutils. As shown by extensive testing, commonly distributed GCC/binutils were likely not reproducing the bug before 2020, but until now this code was commonly built with Clang, also thanks to the distribution they use and for whatever reasons some lucky people don't reproduce the bug even with recent GCC and binutils, this explains why: - some people have not experienced the bug by luck, - some people actually experiencing the bug wrongly believe the code is not meant to build with GCC and then never report it. We were in the second category: we were experiencing the bug, but we never reported it before, other users of the software were in the first category: not reproducing the bug just by luck. But the bug already shipped to users since at least 5 years. -- You are receiving this mail because: You are on the CC list for the bug.
