From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Documentation for .largecomm and friends
Date: Thu, 04 Jan 2018 15:56:00 -0000 [thread overview]
Message-ID: <b408de56-bbd3-5d4e-6c9d-923478670855@redhat.com> (raw)
In-Reply-To: <5A4E5986020000780019B1CC@prv-mh.provo.novell.com>
Hi Jan,
>> Any objections to this patch for PR 22553 ?
>
> Sounds plausible, thanks for doing this. What about "and friends"
> though?
The PR also refers to .lbss, .ldata and .lrodata, but I think that
the reporter was mistaken about those.
There is a comment in gas/doc/c-i386.texi mentioning that .code16gcc
is not documented, and a scan of the code indicates that .secrel32,
.operand_check, .sse_check, .disallow_index_reg, and .allow_index_reg
are also missing documentation.
Cheers
Nick
prev parent reply other threads:[~2018-01-04 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87po7cqauz.fsf@redhat.com>
[not found] ` <5A37F8F10200007800198337@prv-mh.provo.novell.com>
[not found] ` <CAMe9rOrws+T56Ryx69hDGhc48C0w-tmFx3jiGoY=ktmJ_naTAQ@mail.gmail.com>
2018-01-04 15:28 ` Nick Clifton
2018-01-04 15:42 ` Jan Beulich
2018-01-04 15:56 ` Nick Clifton [this message]
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=b408de56-bbd3-5d4e-6c9d-923478670855@redhat.com \
--to=nickc@redhat.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).