public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	HAO CHEN GUI <guihaoc@linux.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	"Kewen.Lin" <linkw@linux.ibm.com>,
	 Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCHv2, rs6000] Enable have_cbranchcc4 on rs6000
Date: Fri, 18 Nov 2022 07:36:09 -0500	[thread overview]
Message-ID: <CAGWvnynvMJvNGXO+VoCSK7PbUBXLJcCk0xapWpUHUTfMEfufdQ@mail.gmail.com> (raw)
In-Reply-To: <20221118121822.GY25951@gate.crashing.org>

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

On Fri, Nov 18, 2022 at 7:20 AM Segher Boessenkool <
segher@kernel.crashing.org> wrote:

> On Fri, Nov 18, 2022 at 02:35:30PM +0800, HAO CHEN GUI wrote:
> > 在 2022/11/17 21:24, David Edelsohn 写道:
> > > Why are you using zero_constant predicate instead of matching
> (const_int 0) for operand 2?
> > The "const_int 0" is an operand other than a predicate. We need a
> predicate here.
>
> Said differently, it is passed as an operand to this named pattern or
> optab, so you need a match_operand here.
>

Earlier versions of patterns for other targets used (const_int 0), but they
seem to have changed that, so match_operand is needed.

Thanks, David


>
> > > Why does this need the new all_branch_comparison_operator?  Can the
> ifcvt optimization correctly elide the 2 insn sequence?
> > Because rs6000 defines "*cbranch_2insn" insn, such insns are generated
> after expand.
> >
> > (jump_insn 50 47 51 11 (set (pc)
> >         (if_then_else (ge (reg:CCFP 156)
> >                 (const_int 0 [0]))
> >             (label_ref 53)
> >             (pc)))
> "/home/guihaoc/gcc/gcc-mainline-base/gmp/mpz/cmpabs_d.c":80:7 884
> {*cbranch_2insn}
> >      (expr_list:REG_DEAD (reg:CCFP 156)
> >         (int_list:REG_BR_PROB 633507684 (nil)))
> >  -> 53)
>
> But notice the cost of *cbranch_2insn -- ifcvt should never generate
> cbranchcc4 with such composite conditions!
>
> > In prepare_cmp_insn, the comparison is verified by insn_operand_matches.
> If
> > extra_insn_branch_comparison_operator is not included in "cbranchcc4"
> predicate,
> > it hits ICE here.
> >
> >   if (GET_MODE_CLASS (mode) == MODE_CC)
> >     {
> >       enum insn_code icode = optab_handler (cbranch_optab, CCmode);
> >       test = gen_rtx_fmt_ee (comparison, VOIDmode, x, y);
> >       gcc_assert (icode != CODE_FOR_nothing
> >                   && insn_operand_matches (icode, 0, test));
> >       *ptest = test;
> >       return;
> >     }
> >
> > The real conditional move is generated by emit_conditional_move_1.
> Commonly
> > "*cbranch_2insn" can't be optimized out and it returns NULL_RTX.
> >
> >       if (COMPARISON_P (comparison))
> >         {
> >           saved_pending_stack_adjust save;
> >           save_pending_stack_adjust (&save);
> >           last = get_last_insn ();
> >           do_pending_stack_adjust ();
> >           machine_mode cmpmode = comp.mode;
> >           prepare_cmp_insn (XEXP (comparison, 0), XEXP (comparison, 1),
> >                             GET_CODE (comparison), NULL_RTX, unsignedp,
> >                             OPTAB_WIDEN, &comparison, &cmpmode);
> >           if (comparison)
> >             {
> >                rtx res = emit_conditional_move_1 (target, comparison,
> >                                                   op2, op3, mode);
> >                if (res != NULL_RTX)
> >                  return res;
> >             }
> >           delete_insns_since (last);
> >           restore_pending_stack_adjust (&save);
> >
> > I think that extra_insn_branch_comparison_operator should be included in
> > "cbranchcc4" predicates as such insns exist. And leave it to
> > emit_conditional_move which decides whether it can be optimized or not.
>
> I don't think we should pretend we have any conditional jumps the
> machine does not actually have, in cbranchcc4.  When would this ever be
> useful?  cror;beq can be quite expensive, compared to the code it would
> replace anyway.
>
> If something generates those here (which then ICEs later), that is
> wrong, fix *that*?  Is it ifcvt doing it?
>
>
> Segher
>

  reply	other threads:[~2022-11-18 12:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  6:39 HAO CHEN GUI
2022-11-17 13:24 ` David Edelsohn
2022-11-18  6:35   ` HAO CHEN GUI
2022-11-18 12:18     ` Segher Boessenkool
2022-11-18 12:36       ` David Edelsohn [this message]
2022-11-21  6:18       ` HAO CHEN GUI
2022-11-21 23:49         ` Segher Boessenkool
2022-11-22  7:50           ` HAO CHEN GUI
2022-11-22  3:11         ` Kewen.Lin
2022-11-22  5:12           ` HAO CHEN GUI
2022-11-22  6:02             ` Kewen.Lin

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=CAGWvnynvMJvNGXO+VoCSK7PbUBXLJcCk0xapWpUHUTfMEfufdQ@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=bergner@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=guihaoc@linux.ibm.com \
    --cc=linkw@linux.ibm.com \
    --cc=segher@kernel.crashing.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).