From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 3EE483858D3C for ; Wed, 22 Feb 2023 08:18:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3EE483858D3C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677053913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=orFtdpP1co+fLMQZKwoIM6NCclM1dRvbypNG0YkGUxA=; b=Ep/d6EpO+T3TbOvFuigE2T7+d1zSrhs1QQtBKBrHflQfiGSQ8ia0aRe3elKZcKu7OLX9rZ LEpCSIQFxsacHPfTIUwXrEo8X3IBDq4ggLVzAdRWcwekGk5jzfgnYgBUMirrqpcR4jje7q Q9mq5LF1QT+dW/NwC3XkdSyLpxWl3is= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-180-nMd4skroPjCminJQzP7O1g-1; Wed, 22 Feb 2023 03:18:31 -0500 X-MC-Unique: nMd4skroPjCminJQzP7O1g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 75762802C18 for ; Wed, 22 Feb 2023 08:18:31 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.2.16.57]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D5C1140C1423 for ; Wed, 22 Feb 2023 08:18:30 +0000 (UTC) From: Florian Weimer To: gcc@gcc.gnu.org Subject: Using __gnu_lto_slim to detect -fno-fat-lto-objects Date: Wed, 22 Feb 2023 09:18:29 +0100 Message-ID: <87a616un8q.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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, Florian