From: Nick Clifton <nickc@redhat.com>
To: Fangrui Song <i@maskray.me>
Cc: binutils@sourceware.org
Subject: Re: RFC: New gas directive: .attach_to_group
Date: Wed, 30 Sep 2020 10:33:21 +0100 [thread overview]
Message-ID: <0854ea7b-8be9-5c77-0fda-2579b81c6aca@redhat.com> (raw)
In-Reply-To: <20200929165317.2yebvny6gas4jz5f@gmail.com>
Hi Fangrui,
> Is this directive an extension to the existing feature: ?
Yes.
> .section .text.foo,"axG",@progbits,group
> .section .rodata.foo,"a?"
The idea being that new directive allows the section group to be
declared at a later date, after the section has been declared. This
is important because two different code generators are involved. GCC
is generating the section declarations and annobin is generating the
section groups.
> If the section group intention of .annobin.text is so that .annobin.text
> can be discarded if the associated .text is discarded (--gc-sections),
It is.
> an alternative is SHF_LINK_ORDER
Hmm, interesting. I shall investigate and see if I can adapt annobin to
use this method. (Which presumably will work with LLVM's assembler as well
as gas).
Cheers
Nick
PS. I see that PR 26253 has not been addressed, sorry about that. I will
try to have a look at it later this week.
next prev parent reply other threads:[~2020-09-30 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 15:12 Nick Clifton
2020-09-29 16:53 ` Fangrui Song
2020-09-30 9:33 ` Nick Clifton [this message]
[not found] ` <3609c590-8750-a021-92fb-05ff0ba7ca7d@redhat.com>
2020-09-30 13:43 ` [PATCH] elf: Also check linked-to section for SHT_NOTE section H.J. Lu
2020-09-30 14:01 ` Nick Clifton
2020-09-30 14:03 ` H.J. Lu
2020-10-01 3:41 ` 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=0854ea7b-8be9-5c77-0fda-2579b81c6aca@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).