public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Christoph Müllner" <christoph.muellner@vrull.eu>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	 Martin Liska <mliska@suse.cz>, Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] doc: invoke: riscv: Fix closing block bracket
Date: Wed, 16 Nov 2022 00:03:25 +0100	[thread overview]
Message-ID: <CAEg0e7hZH6O3_y=4mq0JdFy-3j=Zgd-AKP7x0UtpZqUG3KWQ2w@mail.gmail.com> (raw)
In-Reply-To: <87tu2z96c7.fsf@igel.home>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

On Tue, Nov 15, 2022 at 11:54 PM Andreas Schwab <schwab@linux-m68k.org>
wrote:

> On Nov 15 2022, Christoph Muellner wrote:
>
> > diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> > index 057439a004c..dfac7c85844 100644
> > --- a/gcc/doc/invoke.texi
> > +++ b/gcc/doc/invoke.texi
> > @@ -1220,8 +1220,8 @@ See RS/6000 and PowerPC Options.
> >  -malign-data=@var{type} @gol
> >  -mbig-endian  -mlittle-endian @gol
> >  -mstack-protector-guard=@var{guard}
> -mstack-protector-guard-reg=@var{reg} @gol
> > --mstack-protector-guard-offset=@var{offset}}
> > --mcsr-check -mno-csr-check @gol
> > +-mstack-protector-guard-offset=@var{offset} @gol
> > +-mcsr-check -mno-csr-check @gol}
>
> There should be no @gol at the end of the list.
>

I saw the @gol at the end of the PRU Options list (just above RISC-V).
I will make a v2 where I will remove the @gol from there as well.

Thanks,
Christoph



>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
>

      reply	other threads:[~2022-11-15 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 22:36 Christoph Muellner
2022-11-15 22:54 ` Andreas Schwab
2022-11-15 23:03   ` Christoph Müllner [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='CAEg0e7hZH6O3_y=4mq0JdFy-3j=Zgd-AKP7x0UtpZqUG3KWQ2w@mail.gmail.com' \
    --to=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=mliska@suse.cz \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=schwab@linux-m68k.org \
    /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).