From: Nick Clifton <nickc@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
ruiu@google.com, 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: <c0e26c8d-77d9-504a-38cf-b71306ba2c14@redhat.com> (raw)
In-Reply-To: <mvm5zuxg8wt.fsf@suse.de>
Hi Andreas,
>> I would like to propose adding a new value to this list. A value of 0.
>
> The value of 0 just means the absence of flags, doesn't it?
Right. I just want to make it clear that a value of 0 is allowed
and that it means that there are no special processing semantics required.
The standard, as currently written is not 100% clear on this:
The section data of a SHT_GROUP section is an array of
Elf32_Word entries. The first entry is a flag word. The
remaining entries are a sequence of section header indices.
The following flags are currently defined:
Figure 4-13: Section Group Flags
Name Value
GRP_COMDAT 0x1
GRP_MASKOS 0x0ff00000
GRP_MASKPROC 0xf0000000
GRP_COMDAT
This is a COMDAT group. It may duplicate another COMDAT
[...]
The problem is that this does not make it clear whether a value
of zero is allowed or an error. So all I am really asking for
is some clarification in the wording of this part of the standard.
Cheers
Nick
next parent reply other threads:[~2019-01-09 15: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 [this message]
2019-01-01 0:00 ` Andreas Schwab
2019-01-01 0:00 ` Cary Coutant
2019-01-01 0:00 ` Rui Ueyama via gnu-gabi
[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=c0e26c8d-77d9-504a-38cf-b71306ba2c14@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gnu-gabi@sourceware.org \
--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).