From: will schmidt <will_schmidt@vnet.ibm.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] rs6000: Fix extraneous characters in the documentation
Date: Tue, 06 Oct 2020 10:29:07 -0500 [thread overview]
Message-ID: <e0b0914cc1ab2f3e74197912f8debe928f89f5ab.camel@vnet.ibm.com> (raw)
In-Reply-To: <87imbomngu.fsf@linux.ibm.com>
On Mon, 2020-10-05 at 17:23 -0300, Tulio Magno Quites Machado Filho via Gcc-patches wrote:
> Ping?
+cc Segher :-)
>
> Tulio Magno Quites Machado Filho via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>
> > Replace them with a whitespace in order to avoid artifacts in the HTML
> > document.
> >
> > 2020-08-19 Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
> >
> > gcc/
> > * doc/extend.texi (PowerPC Built-in Functions): Replace
> > extraneous characters with whitespace.
> > ---
> > gcc/doc/extend.texi | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
> > index bcc251481ca..0c380322280 100644
> > --- a/gcc/doc/extend.texi
> > +++ b/gcc/doc/extend.texi
> > @@ -21538,10 +21538,10 @@ void amo_stdat_smin (int64_t *, int64_t);
> > ISA 3.1 of the PowerPC added new Matrix-Multiply Assist (MMA) instructions.
> > GCC provides support for these instructions through the following built-in
> > functions which are enabled with the @code{-mmma} option. The vec_t type
> > -below is defined to be a normal vector unsigned char type. The uint2, uint4
> > +below is defined to be a normal vector unsigned char type. The uint2, uint4
That looks like a non-breaking space. (ascii c2 a0) so
2e c2 a0 20 becomes 2e 20 20
> > and uint8 parameters are 2-bit, 4-bit and 8-bit unsigned integer constants
> > -respectively. The compiler will verify that they are constants and that
> > -their values are within range.
> > +respectively. The compiler will verify that they are constants and that
> > +their values are within range.
2e c2 a0 20 becomes 2e 20 20
And drops a trailing whitespace.
Those seem reasonable.
lgtm
Thanks
-Will
> >
> > The built-in functions supported are:
> >
> > --
> > 2.25.4
> >
>
>
next prev parent reply other threads:[~2020-10-06 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 19:03 Tulio Magno Quites Machado Filho
2020-10-05 20:23 ` Tulio Magno Quites Machado Filho
2020-10-06 15:29 ` will schmidt [this message]
2020-10-07 23:48 ` Segher Boessenkool
2020-10-23 15:12 ` Segher Boessenkool
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=e0b0914cc1ab2f3e74197912f8debe928f89f5ab.camel@vnet.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tuliom@linux.ibm.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).