* Re: Documentation for .largecomm and friends [not found] ` <CAMe9rOrws+T56Ryx69hDGhc48C0w-tmFx3jiGoY=ktmJ_naTAQ@mail.gmail.com> @ 2018-01-04 15:28 ` Nick Clifton 2018-01-04 15:42 ` Jan Beulich 0 siblings, 1 reply; 3+ messages in thread From: Nick Clifton @ 2018-01-04 15:28 UTC (permalink / raw) To: H.J. Lu, Jan Beulich, binutils Hi H.J., Hi Jan, Any objections to this patch for PR 22553 ? Cheers Nick diff --git a/gas/doc/c-i386.texi b/gas/doc/c-i386.texi index 91f5c5a21a..e500e7c86d 100644 --- a/gas/doc/c-i386.texi +++ b/gas/doc/c-i386.texi @@ -431,8 +431,17 @@ specifies the desired alignment of the symbol in the bss section. This directive is only available for COFF based x86 targets. +@cindex @code{largecomm} directive, ELF +@item .largecomm @var{symbol} , @var{length}[, @var{alignment}] +This directive behaves in the same way as the @code{comm} directive +except that the data is placed into the @var{.lbss} section instead of +the @var{.bss} section @ref{Comm}. + +The directive is intended to be used for data which requires a large +amount of space, and it is only available for ELF based x86_64 +targets. + @c FIXME: Document other x86 specific directives ? Eg: .code16gcc, -@c .largecomm @end table ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Documentation for .largecomm and friends 2018-01-04 15:28 ` Documentation for .largecomm and friends Nick Clifton @ 2018-01-04 15:42 ` Jan Beulich 2018-01-04 15:56 ` Nick Clifton 0 siblings, 1 reply; 3+ messages in thread From: Jan Beulich @ 2018-01-04 15:42 UTC (permalink / raw) To: Nick Clifton; +Cc: H.J. Lu, binutils >>> On 04.01.18 at 16:28, <nickc@redhat.com> wrote: > Hi H.J., Hi Jan, > > Any objections to this patch for PR 22553 ? Sounds plausible, thanks for doing this. What about "and friends" though? Jan > --- a/gas/doc/c-i386.texi > +++ b/gas/doc/c-i386.texi > @@ -431,8 +431,17 @@ specifies the desired alignment of the symbol in the > bss section. > > This directive is only available for COFF based x86 targets. > > +@cindex @code{largecomm} directive, ELF > +@item .largecomm @var{symbol} , @var{length}[, @var{alignment}] > +This directive behaves in the same way as the @code{comm} directive > +except that the data is placed into the @var{.lbss} section instead of > +the @var{.bss} section @ref{Comm}. > + > +The directive is intended to be used for data which requires a large > +amount of space, and it is only available for ELF based x86_64 > +targets. > + > @c FIXME: Document other x86 specific directives ? Eg: .code16gcc, > -@c .largecomm > > @end table > ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Documentation for .largecomm and friends 2018-01-04 15:42 ` Jan Beulich @ 2018-01-04 15:56 ` Nick Clifton 0 siblings, 0 replies; 3+ messages in thread From: Nick Clifton @ 2018-01-04 15:56 UTC (permalink / raw) To: Jan Beulich; +Cc: H.J. Lu, binutils 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 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-01-04 15:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 ` Documentation for .largecomm and friends Nick Clifton
2018-01-04 15:42 ` Jan Beulich
2018-01-04 15:56 ` Nick Clifton
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).