mirror of
https://forge.sourceware.org/marek/gcc.git
synced 2026-02-22 12:00:11 -05:00
6051a849aa
commit aef88b83384976e96a8fb287a001588a2277ecd5 Author: H.J. Lu <hjl.tools@gmail.com> Date: Thu Oct 2 08:53:45 2025 +0800 binutils/GCC: Quote ${COMPILER_FOR_TARGET} Replace if test x${COMPILER_FOR_TARGET} = x"\$(CC)"; then with if test x"${COMPILER_FOR_TARGET}" = x"\$(CC)"; then since COMPILER_FOR_TARGET may contain spaces when configuring GCC. commit 76a693c087c30e8108852928c717399011c6166d Author: H.J. Lu <hjl.tools@gmail.com> Date: Tue Sep 30 11:23:58 2025 +0800 binutils: Use AC_TRY_COMPILE to check target clang/gcc Use AC_TRY_COMPILE to check for the working target clang and gcc when configuring for cross tools. commit 77c74294bfc5005204a2de3cc64bbdb2f877be29 Author: H.J. Lu <hjl.tools@gmail.com> Date: Fri Sep 26 08:03:01 2025 +0800 binutils: Pass target plugin file to target ar/nm/ranlib There are 2 kinds of binutils tests: 1. Tests of binutils object files and libraries using the build tools, like CC, AR, NM and RANLIB. 2. Tests of binutils programs as the target tools, like CC_FOR_TARGET, AR_FOR_TARGET, NM_FOR_TARGET and RANLIB_FOR_TARGET. Set AR_PLUGIN_OPTION_FOR_TARGET, NM_PLUGIN_OPTION_FOR_TARGET and RANLIB_PLUGIN_OPTION_FOR_TARGET to the target compiler plugin file for target ar/nm/ranlib. commit 10deea6e2fc1b9ec5818b5fa1bc510c63ff5b2e2 Author: H.J. Lu <hjl.tools@gmail.com> Date: Tue Sep 23 04:24:00 2025 +0800 Binutils/GCC: Add clang LTO support to AR, NM and RANLIB Add CLANG_PLUGIN_FILE to find the clang plugin file and pass it to --plugin for ar, nm and ranlib so that binutils can be built with clang LTO. Run CLANG_PLUGIN_FILE before GCC_PLUGIN_OPTION since GCC_PLUGIN_OPTION may return the wrong PLUGIN_OPTION with clang. commit 1fcb94ed750db2ac30d0f0ecc04fa0c7833dd10f Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Date: Thu Sep 18 16:17:14 2025 +0200 Remove remnants of Solaris/PowerPC support When removing Solaris/PowerPC support, I missed a couple of references. This patch removes them. Tested with crosses to ppc-unknown-linux-gnu and powerpc-ibm-aix7. ChangeLog: * Makefile.in: Regenerated. * configure: Likewise. * Makefile.tpl: Synced from binutils-gdb. * configure.ac: Likewise. * libtool.m4: Likewise. config/ChangeLog: * clang-plugin.m4: Synced from binutils-gdb. * gcc-plugin.m4: Likewise. libbacktrace/ChangeLog: * Makefile.in: Regenerated. * aclocal.m4: Likewise. * configure: Likewise. libiberty/ChangeLog: * aclocal.m4: Regenerated. * configure: Likewise. * configure.ac: Synced from binutils-gdb. zlib/ChangeLog: * Makefile.in: Regenerated. * aclocal.m4: Likewise. * configure: Likewise. Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
The libbacktrace library Initially written by Ian Lance Taylor <iant@golang.org> The libbacktrace library may be linked into a program or library and used to produce symbolic backtraces. Sample uses would be to print a detailed backtrace when an error occurs or to gather detailed profiling information. In general the functions provided by this library are async-signal-safe, meaning that they may be safely called from a signal handler. That said, on systems that use dl_iterate_phdr, such as GNU/Linux, the first call to a libbacktrace function will call dl_iterate_phdr, which is not in general async-signal-safe. Therefore, programs that call libbacktrace from a signal handler should ensure that they make an initial call from outside of a signal handler. Similar considerations apply when arranging to call libbacktrace from within malloc; dl_iterate_phdr can also call malloc, so make an initial call to a libbacktrace function outside of malloc before trying to call libbacktrace functions within malloc. The libbacktrace library is provided under a BSD license. See the source files for the exact license text. The public functions are declared and documented in the header file backtrace.h, which should be #include'd by a user of the library. Building libbacktrace will generate a file backtrace-supported.h, which a user of the library may use to determine whether backtraces will work. See the source file backtrace-supported.h.in for the macros that it defines. As of July 2024, libbacktrace supports ELF, PE/COFF, Mach-O, and XCOFF executables with DWARF debugging information. In other words, it supports GNU/Linux, *BSD, macOS, Windows, and AIX. The library is written to make it straightforward to add support for other object file and debugging formats. The library relies on the C++ unwind API defined at https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html This API is provided by GCC and clang.