From: Robin Dapp <rdapp@linux.ibm.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH v3 5/7] ifcvt: Try re-using CC for conditional moves.
Date: Mon, 10 Jan 2022 12:18:22 +0100 [thread overview]
Message-ID: <8c203bd5-eac8-44ab-00c7-436c98472af1@linux.ibm.com> (raw)
In-Reply-To: <7e96ba73-e96f-ecf5-8011-32ef24e49096@gmail.com>
Posting the ChangeLog before pushing.
--
gcc/ChangeLog:
* ifcvt.c (cond_exec_get_condition): New parameter to allow getting the
reversed comparison.
(try_emit_cmove_seq): New function to facilitate creating a cmov
sequence.
(noce_convert_multiple_sets): Create two sequences and use the less
expensive one.
next prev parent reply other threads:[~2022-01-10 11:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 18:43 [PATCH v3 0/7] ifcvt: Convert multiple Robin Dapp
2021-12-06 18:43 ` [PATCH v3 1/7] ifcvt: Check if cmovs are needed Robin Dapp
2021-12-09 1:26 ` Jeff Law
2022-01-10 11:17 ` Robin Dapp
2021-12-06 18:43 ` [PATCH v3 2/7] ifcvt: Allow constants for noce_convert_multiple Robin Dapp
2021-12-08 23:51 ` Jeff Law
2022-01-10 11:17 ` Robin Dapp
2021-12-06 18:43 ` [PATCH v3 3/7] ifcvt: Improve costs handling " Robin Dapp
2021-12-08 23:54 ` Jeff Law
2022-01-10 11:17 ` Robin Dapp
2021-12-06 18:43 ` [PATCH v3 4/7] ifcvt/optabs: Allow using a CC comparison for emit_conditional_move Robin Dapp
2021-12-09 0:11 ` Jeff Law
2021-12-09 17:20 ` Robin Dapp
2021-12-09 17:34 ` Jeff Law
2022-01-10 11:18 ` Robin Dapp
2021-12-06 18:43 ` [PATCH v3 5/7] ifcvt: Try re-using CC for conditional moves Robin Dapp
2021-12-09 1:18 ` Jeff Law
2022-01-10 11:18 ` Robin Dapp [this message]
2021-12-06 18:43 ` [PATCH v3 6/7] testsuite/s390: Add tests for noce_convert_multiple Robin Dapp
2021-12-08 23:48 ` Jeff Law
2022-01-10 11:18 ` Robin Dapp
2021-12-06 18:43 ` [PATCH v3 7/7] ifcvt: Run second pass if it is possible to omit a temporary Robin Dapp
2021-12-09 1:24 ` Jeff Law
2021-12-10 15:06 ` Robin Dapp
2021-12-15 20:24 ` Jeff Law
2022-01-10 11:18 ` Robin Dapp
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=8c203bd5-eac8-44ab-00c7-436c98472af1@linux.ibm.com \
--to=rdapp@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).