From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fweimer@redhat.com>
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 921CF3858C78
 for <gcc-help@gcc.gnu.org>; Tue,  1 Mar 2022 11:19:22 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 921CF3858C78
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-380-JpXnDvYnPj-flZJ2EUzr1Q-1; Tue, 01 Mar 2022 06:19:21 -0500
X-MC-Unique: JpXnDvYnPj-flZJ2EUzr1Q-1
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com
 [10.5.11.22])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 31868800422
 for <gcc-help@gcc.gnu.org>; Tue,  1 Mar 2022 11:19:20 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.39.193.76])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id 749ED1053B06
 for <gcc-help@gcc.gnu.org>; Tue,  1 Mar 2022 11:19:19 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: gcc-help@gcc.gnu.org
Subject: Defining something as constant for linking purposes only
Date: Tue, 01 Mar 2022 12:19:17 +0100
Message-ID: <877d9dq5sa.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gcc-help@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-help mailing list <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2022 11:19:23 -0000

Is there a recommended way to define a data object as constant, while
preventing GCC from making any assumptions regarding the value of the
constant?

Separate compilation breaks under LTO.

This is interesting for data objects whose final value is patched into
the binary after the build has completed and the final link took place.

Thanks,
Florian