https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88262
--- Comment #19 from Stephen Kim <stephen.kim at oracle dot com> --- Thank you for all of your comments! I have talked with our team members again. It seems that there has been miscommunication. They seemed to have intended that Go tools should give Scrt1.o. However, as Go tools is just an ordinary client of gcc (and clang or whatsoever), I believed that Go tools is not supposed to know about Scrt1.o or crt1.o. They are internals. That made me think that the gcc driver must be the culprit. However, it seems that the gcc driver is supposed to give crt1.o, and I could now convince myself. If that's the case, this issue should be resolved either in glibc or gold. Thanks again!
