From: "Rui Ueyama via gnu-gabi" <gnu-gabi@sourceware.org>
To: Cary Coutant <ccoutant@gmail.com>
Cc: Andreas Schwab <schwab@suse.de>, Nick Clifton <nickc@redhat.com>,
"binutils@sourceware.org" <binutils@sourceware.org>,
Peter Smith <peter.smith@linaro.org>,
sguelton@redhat.com, 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: <CAJENXgs1SynxQ5ZYv1d4OmBoW_dxtjsJT+1C3ja+CfpaC-R8RQ@mail.gmail.com> (raw)
In-Reply-To: <CAJimCsGG-3yY2ww5c1=9xY7YaunFLMJp=0S5ZtwVYEquf7WeRg@mail.gmail.com>
After carefully reading the page (*), I also found that the value 0
can be interpreted as an absence of any flag and has no semantics
other than defining a group, which would probably means that they
should be discarded or retained as a group when GC runs. But I don't
think it is very clear; we probably should add a clarifying statement
to the spec.
* https://docs.oracle.com/cd/E19120-01/open.solaris/819-0690/chapter7-26/index.html
On Wed, Jan 9, 2019 at 10:11 AM Cary Coutant <ccoutant@gmail.com> wrote:
>
> > > The problem is that this does not make it clear whether a value
> > > of zero is allowed or an error.
> >
> > Why would the absence of flag 0 be different from the absence of any
> > other flag?
>
> I'm OK with adding a clarifying statement to the spec.
>
> -cary
next prev parent reply other threads:[~2019-01-09 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] <000000000000e0ce64057f1c76ed@google.com>
2019-01-01 0:00 ` Nick Clifton
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=CAJENXgs1SynxQ5ZYv1d4OmBoW_dxtjsJT+1C3ja+CfpaC-R8RQ@mail.gmail.com \
--to=gnu-gabi@sourceware.org \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=nickc@redhat.com \
--cc=peter.smith@linaro.org \
--cc=ruiu@google.com \
--cc=schwab@suse.de \
--cc=sguelton@redhat.com \
/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).