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 [thread overview]
Message-ID: <877d9dq5sa.fsf@oldenburg.str.redhat.com> (raw)
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
reply other threads:[~2022-03-01 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d9dq5sa.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).