gcc-10-20230302 is now available
Snapshot gcc-10-20230302 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20230302/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-10 revision 9e6a3a70b70b6ab16ebbc3ee0b4165378327e453 You'll find: gcc-10-20230302.tar.xz Complete GCC SHA256=4dd600038f9d48af467161adea5f144347e9e5ac1c53cac93e53166303cf0c2d SHA1=eff5b88d1e5867e01350d0f3cc9c14a386562c89 Diffs from 10-20230223 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-10 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Using __gnu_lto_slim to detect -fno-fat-lto-objects
On 2/22/23 01:18, Florian Weimer via Gcc wrote: Can we use the COMMON symbol __gnu_lto_slim to detect -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker plugin)? We currently build the distribution with -ffat-lto-objects, and I want to switch away from that. Packages will need to opt in to -ffat-lto-objects if static objects they build escape the buildroot. And to make sure that this opt-in happens, I want to fail the build if there would be any -fno-fat-lto-objects objects leaking. Thanks for taking care of this. It's one of the things I wish I'd had time to fix before leaving Red Hat. We burn a fair amount of builder time due to this issue right now. jeff
