From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: Use cbranch optabs in ifcvt.c
Date: Mon, 24 Aug 2015 17:00:00 -0000 [thread overview]
Message-ID: <55DB4B08.5010805@redhat.com> (raw)
In-Reply-To: <87oahx6igk.fsf@e105548-lin.cambridge.arm.com>
On 08/24/2015 05:20 AM, Richard Sandiford wrote:
> Similarly to the patch for cmpstr(n), this patch uses the optabs
> interface for cbranchcc4 instead of using HAVE_cbranchcc4 directly.
> I've cached the result in a pass-local variable (valid only for
> the duration of the pass).
>
> The references to incscc and decscc are dead. The only reference
> to them in the documentation is:
>
> Some machines can also perform @code{and} or @code{plus} operations on
> condition code values with less instructions than the corresponding
> @samp{cstore@var{mode}4} insn followed by @code{and} or @code{plus}. On those
> machines, define the appropriate patterns. Use the names @code{incscc}
> and @code{decscc}, respectively, for the patterns which perform
> @code{plus} or @code{minus} operations on condition code values. See
> @file{rs6000.md} for some examples. The GNU Superoptimizer can be used to
> find such instruction sequences on other machines.
>
> which is in tm.texi rather than md.texi. This seems hopelessly out of
> date, not least because rs6000.md has no incscc or decscc patterns.
> If the "appropriate patterns" are just combine patterns, perhaps we
> should just delete the whole paragraph?
I think the whole paragraph should just go away. We don't do anything
with those special patterns anymore. The PA still defines them, but
they're just combiner patterns in the end.
>
> Tested on x86_64-linux-gnu. OK to install?
>
> Thanks,
> Richard
>
> gcc/
> * ifcvt.c (HAVE_incscc, HAVE_decscc, HAVE_cbranchcc4): Delete.
> (have_cbranchcc4): New variable.
> (cc_in_cond, noce_emit_cmove, noce_get_alt_condition)
> (noce_get_condition): Use it instead of HAVE_cbranchcc4.
> (if_convert): Initialize have_cbranchcc4.
OK.
jeff
prev parent reply other threads:[~2015-08-24 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 11:23 Richard Sandiford
2015-08-24 17:00 ` Jeff Law [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=55DB4B08.5010805@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).