public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: gnu-gabi@sourceware.org
Subject: Re: RFC Adding a section group flag of 0
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <c81a7282-9147-05e0-c959-e3c2d8e101f5@redhat.com> (raw)
In-Reply-To: <000000000000e0ce64057f1c76ed@google.com>

Hi Ali,

  [I tried posting this to generic-abi@googlegroups.com but it was rejected.
  I hope that it will reach you via the gnu-gabi email address].

> Nick, I am curious why gcc produces these GROUP sections. Not
> challenging their right to do so, but wondering what benefit
> they derive from it.

It is not gcc itself.  It is the annobin plugin to gcc.  The plugin
creates new note sections to describe the contents of any code
section created by gcc.  It puts the note section and the code section
together into a group so that if the linker discards the code section
it will also discard the note section.

The notes are used by a security checking tool in order to make sure
that the code has been compiled according to a specified set of
guidelines.  In order for this to work, accurate notes are needed and
having extraneous notes referring to discarded code sections would
be a bad thing.

Cheers
  Nick

PS.  If you are interested in the actual code, it is under the GPL.
Check out the annobin package in Fedora.  The specification for
the notes is also available here:

  https://fedoraproject.org/wiki/Toolchain/Watermark

       reply	other threads:[~2019-01-10 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000e0ce64057f1c76ed@google.com>
2019-01-01  0:00 ` Nick Clifton [this message]
     [not found] <24c0c8d8-44e6-ab81-bdfb-43af8b53323b@redhat.com>
     [not found] ` <mvm5zuxg8wt.fsf@suse.de>
2019-01-01  0:00   ` Nick Clifton
2019-01-01  0:00     ` Andreas Schwab
2019-01-01  0:00       ` Cary Coutant
2019-01-01  0:00         ` Rui Ueyama via gnu-gabi

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=c81a7282-9147-05e0-c959-e3c2d8e101f5@redhat.com \
    --to=nickc@redhat.com \
    --cc=gnu-gabi@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).