https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88262
--- Comment #14 from Stephen Kim <stephen.kim at oracle dot com> --- (In reply to Andreas Schwab from comment #7) > If you think you have found a bug in glibc, then this is not the right place > to report it. I believe that this is NOT a glibc bug. It is TRIGGERED by a glibc patch. I would say that the glibc patch is legitimate. Personally, I believe that this is a compiler driver bug. That's why I am filing the bug here. Even now, I am not convinced that this is not a gcc bug.(In reply to Andrew Pinski from comment #10) > This could also be a gold linker issue too. > > But then again this is not the right place to report a gold or glibc issue. > Try https://sourceware.org/bugzilla/ instead. Regarding Gold, I have talked with Ian Lance Taylor, who is known to be an author of gold and who I believe is a linker expert. He does not think that this bug is a Gold issue. According to his emails, he seems to believe that Gold should be given Scrt1.o.