From: Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
To: binutils@sourceware.org
Subject: [PATCH v2 0/6] gas: Add support for LLVM addrsig and addrsig_sym.
Date: Fri, 24 Jun 2022 00:13:48 +0900 [thread overview]
Message-ID: <20220623151353.62139-1-ishitatsuyuki@gmail.com> (raw)
LLVM's addrsig extension [1] allows the compiler to pass on information
about whether a symbol's address is taken to the linker, which in turns
use this info to perform (safe) Identical Code Folding optimization at
link-time.
This patch adds support for the relevant LLVM assembler directives,
which is a prerequisite for GCC support of the feature.
v2 includes patch to objcopy and ld -r to discard the .llvm_addrsig
section, in order to prevent linkers to get corrupted input now that
the SH_LINK heuristic they use is supplied with the proper value.
Thanks Alan Modra, Fangrui Song and Jan Beulich for reviewing the last
revision of the patch.
[1]: https://llvm.org/docs/Extensions.html#sht-llvm-addrsig-section-address-significance-table
next reply other threads:[~2022-06-23 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 15:13 Tatsuyuki Ishi [this message]
2022-06-23 15:13 ` [PATCH v2 1/6] elf: Add definition for SHT_LLVM_ADDRSIG Tatsuyuki Ishi
2022-06-23 15:13 ` [PATCH v2 2/6] bfd: Output SH_LINK to .symtab " Tatsuyuki Ishi
2022-06-23 15:13 ` [PATCH v2 3/6] objcopy: Remove SHT_LLVM_ADDRSIG sections by default Tatsuyuki Ishi
2022-06-23 15:40 ` Jan Beulich
2022-06-24 5:28 ` Tatsuyuki Ishi
2022-06-23 15:13 ` [PATCH v2 4/6] ld: Discard LLVM_ADDRSIG sections Tatsuyuki Ishi
2022-06-23 15:13 ` [PATCH v2 5/6] gas: Add support for LLVM addrsig and addrsig_sym directives on ELF Tatsuyuki Ishi
2022-06-23 15:13 ` [PATCH v2 6/6] gas: Add basic test for addrsig Tatsuyuki Ishi
2022-06-28 9:20 ` [PATCH v2 0/6] gas: Add support for LLVM addrsig and addrsig_sym Alan Modra
2022-06-29 1:27 ` Tatsuyuki Ishi
2022-06-29 2:56 ` Alan Modra
2022-06-30 20:59 ` Fangrui Song
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=20220623151353.62139-1-ishitatsuyuki@gmail.com \
--to=ishitatsuyuki@gmail.com \
--cc=binutils@sourceware.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).