mirror of
https://github.com/gcc-mirror/gcc.git
synced 2026-05-06 14:59:39 +02:00
34039b22ad
So, apparently I've tripped over not just one linker bug with the libatomic/libgcc_s asneeded workaround for libtool bug, but two. One is that mold doesn't parse INPUT ( AS_NEEDED ( -latomic ) ) or INPUT ( AS_NEEDED ( -lgcc_s ) ) correctly, I think that just should be fixed in mold. Another one is that ld.bfd doesn't handle correctly INPUT ( libatomic.a ) when doing static linking with -flto. While that bug should be fixed too in the linker, the reason to install a linker script for a static library has been just my laziness, a symbolic link is more efficient, and even on hosts without symbolic link for a very small library like libatomic.a we can live with a cp -pR copy of it. Furthermore, when I was checking in the last patch (i.e. r16-6736 PR123396), git was loudly complaining about libatomic_asneeded.a being checked into repository when *.a is in .gitignored. So, the following patch revamps the libatomic_asneeded* handling. libatomic_asneeded.so is rewritten in the way that libgcc_s_asneeded.so is done and libatomic_asneeded.a installed using $(LN_S). 2026-01-19 Jakub Jelinek <jakub@redhat.com> PR libgcc/123650 * Makefile.am (toolexeclib_DATA): Remove. (all-local): For LIBAT_BUILD_ASNEEDED_SOLINK instead of installing libatomic_asneeded.{so,a} from top_srcdir cd into the destination directory, use echo to write libatomic_asneeded.so and $(LN_S) to symlink libatomic_asneeded.a to libatomic.a. (install-data-am): For LIBAT_BUILD_ASNEEDED_SOLINK depend on install-asneeded. (install-asneeded): New goal. * libatomic_asneeded.so: Remove. * libatomic_asneeded.a: Remove. * Makefile.in: Regenerate.
This directory contains the GNU Compiler Collection (GCC). The GNU Compiler Collection is free software. See the files whose names start with COPYING for copying permission. The manuals, and some of the runtime libraries, are under different terms; see the individual source files for details. The directory INSTALL contains copies of the installation information as HTML and plain text. The source of this information is gcc/doc/install.texi. The installation information includes details of what is included in the GCC sources and what files GCC installs. See the file gcc/doc/gcc.texi (together with other files that it includes) for usage and porting information. An online readable version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. Copyright years on GCC source files may be listed using range notation, e.g., 1987-2012, indicating that every year in the range, inclusive, is a copyrightable year that could otherwise be listed individually.