From: Jeff Law <jeffreyalaw@gmail.com>
To: Takayuki 'January June' Suwa <jjsuwa_sys3175@yahoo.co.jp>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] ifcvt.cc: Prevent excessive if-conversion for conditional moves
Date: Sat, 11 Mar 2023 09:30:20 -0700 [thread overview]
Message-ID: <0d135ac7-0cd7-5fb6-595f-50682a93bb50@gmail.com> (raw)
In-Reply-To: <076a3744-f608-6f31-7244-2bf7ab06cdb1@yahoo.co.jp>
On 1/10/23 21:20, Takayuki 'January June' Suwa via Gcc-patches wrote:
> Currently, cond_move_process_if_block() does the conversion without
> balancing the cost of the converted sequence with the original one, but
> this should be checked by calling targetm.noce_conversion_profitable_p().
>
> Doing so allows us to provide a way based on the target-specific cost
> estimate, to prevent unwanted size growth due to excessive conditional
> moves on optimizing for size.
>
> On optimizing for speed, default_noce_conversion_profitable_p() allows
> plenty of headroom, so this patch has little impact.
>
> Also, if the target-specific cost estimate is accurate or allows for
> margins, the impact should be similarly small.
>
> gcc/ChangeLog:
>
> * ifcvt.cc (cond_move_process_if_block):
> Consider the result of targetm.noce_conversion_profitable_p()
> when replacing the original sequence with the converted one.
This is OK for gcc-14 when stage1 opens. The only way I see including
it in gcc-13 would be if it fixes a regression.
jeff
next prev parent reply other threads:[~2023-03-11 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <076a3744-f608-6f31-7244-2bf7ab06cdb1.ref@yahoo.co.jp>
2023-01-11 4:20 ` Takayuki 'January June' Suwa
2023-01-11 8:02 ` Robin Dapp
2023-01-12 3:34 ` Takayuki 'January June' Suwa
2023-03-11 16:30 ` Jeff Law [this message]
2023-04-18 20:12 ` Jeff Law
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=0d135ac7-0cd7-5fb6-595f-50682a93bb50@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jjsuwa_sys3175@yahoo.co.jp \
/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).