From: Jakub Jelinek <jakub@redhat.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] Document new overflow arithmetics patterns
Date: Fri, 20 Nov 2015 10:37:00 -0000 [thread overview]
Message-ID: <20151120103708.GG5675@tucnak.redhat.com> (raw)
In-Reply-To: <1557052.Jl1FD73nyu@polaris>
On Fri, Nov 20, 2015 at 11:12:06AM +0100, Eric Botcazou wrote:
> Hi,
>
> this documents the new overflow arithmetics patterns added recently (addv4,
> subv4, mulv4, umulv4, negv3) and only them, i.e. the old ones are still not.
> This also fixes the description of the cbranch and jump patterns, which were
> referring to a label_ref instead of a code_label.
>
> Tested with 'make doc' on x86-64/Linux, OK for mainline and 5 branch?
>
>
> 2015-11-20 Eric Botcazou <ebotcazou@adacore.com>
>
> * doc/md.texi (Standard Names): Move entry for addptr3 around,
> add entries for addv4, subv4, mulv4, umulv4 and negv3, fixes
> glitch in entries for cbranch4 and jump.
Ok, thanks.
> +@cindex @code{negv@var{m}3} instruction pattern
> +@item @samp{negv@var{m}3}
> +Like @code{neg@var{m}2} but takes a @code{code_label} as operand 2 and
> +emits code to jump to it if signed overflow occurs during the negation.
Spurious space before "but".
Jakub
prev parent reply other threads:[~2015-11-20 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 10:12 Eric Botcazou
2015-11-20 10:37 ` Jakub Jelinek [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=20151120103708.GG5675@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.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).