public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp@linux.ibm.com>
To: Claudiu Zissulescu <claziss@gmail.com>,
	gcc-patches@gcc.gnu.org, fbedard@synopsys.com,
	Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [committed] arc: Fail conditional move expand patterns
Date: Fri, 25 Feb 2022 14:29:40 +0100	[thread overview]
Message-ID: <534c0eea-39bb-e927-cceb-802e89b766ed@linux.ibm.com> (raw)
In-Reply-To: <20220225125057.1230923-1-claziss@synopsys.com>

> If the movcc comparison is not valid it triggers an assert in the
> current implementation.  This behavior is not needed as we can FAIL
> the movcc expand pattern.

In case of a MODE_CC comparison you can also just return it as described
here https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104154

or here: https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590639.html

If there already is a "CC comparison" the backend does not need to
create one and ifcvt can make use of this, creating better sequences.

Regards
 Robin

  reply	other threads:[~2022-02-25 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 12:50 Claudiu Zissulescu
2022-02-25 13:29 ` Robin Dapp [this message]
2022-02-28  9:45   ` Claudiu Zissulescu Ianculescu

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=534c0eea-39bb-e927-cceb-802e89b766ed@linux.ibm.com \
    --to=rdapp@linux.ibm.com \
    --cc=claziss@gmail.com \
    --cc=fbedard@synopsys.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.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).