| Message ID | 20200712235255.7918-1-jimw@sifive.com |
|---|---|
| State | New |
| Headers | show |
| Series | aarch64: Delete duplicated option docs. | expand |
Ping. ccing the aarch64 maintainers. If I don't get a response, I will just commit this as obvious. Jim On Sun, Jul 12, 2020 at 4:52 PM Jim Wilson <jimw@sifive.com> wrote: > > Noticed while reviewing the RISC-V -mstack-protector-guard docs. The, and could maybe be added as a separate patch. > AArch64 section has two identical copies of the docs for this option. > > * doc/invoke.texi (AArch64 Options): Delete duplicate > -mstack-protector-guard docs. > --- > gcc/doc/invoke.texi | 18 ------------------ > 1 file changed, 18 deletions(-) > > diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi > index 09bcc5b0f78..2d5803a781b 100644 > --- a/gcc/doc/invoke.texi > +++ b/gcc/doc/invoke.texi > @@ -17126,24 +17126,6 @@ and from what offset from that base register. There is no default > register or offset as this is entirely for use within the Linux > kernel. > > -@item -mstack-protector-guard=@var{guard} > -@itemx -mstack-protector-guard-reg=@var{reg} > -@itemx -mstack-protector-guard-offset=@var{offset} > -@opindex mstack-protector-guard > -@opindex mstack-protector-guard-reg > -@opindex mstack-protector-guard-offset > -Generate stack protection code using canary at @var{guard}. Supported > -locations are @samp{global} for a global canary or @samp{sysreg} for a > -canary in an appropriate system register. > - > -With the latter choice the options > -@option{-mstack-protector-guard-reg=@var{reg}} and > -@option{-mstack-protector-guard-offset=@var{offset}} furthermore specify > -which system register to use as base register for reading the canary, > -and from what offset from that base register. There is no default > -register or offset as this is entirely for use within the Linux > -kernel. > - > @item -mtls-dialect=desc > @opindex mtls-dialect=desc > Use TLS descriptors as the thread-local storage mechanism for dynamic accesses > -- > 2.17.1 >
Jim Wilson <jimw@sifive.com> writes: > Ping. ccing the aarch64 maintainers. If I don't get a response, I > will just commit this as obvious. OK, thanks. Sorry, I hadn't realised the original message was an RFA rather than a post-commit thing. Richard
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 09bcc5b0f78..2d5803a781b 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -17126,24 +17126,6 @@ and from what offset from that base register. There is no default register or offset as this is entirely for use within the Linux kernel. -@item -mstack-protector-guard=@var{guard} -@itemx -mstack-protector-guard-reg=@var{reg} -@itemx -mstack-protector-guard-offset=@var{offset} -@opindex mstack-protector-guard -@opindex mstack-protector-guard-reg -@opindex mstack-protector-guard-offset -Generate stack protection code using canary at @var{guard}. Supported -locations are @samp{global} for a global canary or @samp{sysreg} for a -canary in an appropriate system register. - -With the latter choice the options -@option{-mstack-protector-guard-reg=@var{reg}} and -@option{-mstack-protector-guard-offset=@var{offset}} furthermore specify -which system register to use as base register for reading the canary, -and from what offset from that base register. There is no default -register or offset as this is entirely for use within the Linux -kernel. - @item -mtls-dialect=desc @opindex mtls-dialect=desc Use TLS descriptors as the thread-local storage mechanism for dynamic accesses