public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105740] missed optimization switch transformation for conditions with duplicate conditions
Date: Tue, 21 Jun 2022 09:29:46 +0000	[thread overview]
Message-ID: <bug-105740-4-PeJyhbZ0iF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105740-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105740

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Xiong Hu Luo <luoxhu@gcc.gnu.org>:

https://gcc.gnu.org/g:57424087e82db140c06d4ea73f9700d5291c5bc2

commit r13-1184-g57424087e82db140c06d4ea73f9700d5291c5bc2
Author: Xionghu Luo <xionghuluo@tencent.com>
Date:   Thu Jun 9 15:46:30 2022 +0800

    if-to-switch: Don't skip the first condition bb when find_conditions in
if-to-switch [PR105740]

    The if condition is at last of first bb, so side effect statement in first
BB
    doesn't matter, then the first if condition could also be folded to switch
    table.

    gcc/ChangeLog:

            PR target/105740
            * gimple-if-to-switch.cc (find_conditions): Don't skip the first
            condition bb.

    gcc/testsuite/ChangeLog:

            PR target/105740
            * gcc.dg/tree-ssa/if-to-switch-11.c: New test.

    Signed-off-by: Xionghu Luo <xionghuluo@tencent.com>

  parent reply	other threads:[~2022-06-21  9:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 11:26 [Bug tree-optimization/105740] New: " b.buschinski at googlemail dot com
2022-05-30  9:57 ` [Bug tree-optimization/105740] " marxin at gcc dot gnu.org
2022-06-21  2:45 ` luoxhu at gcc dot gnu.org
2022-06-21  7:30 ` marxin at gcc dot gnu.org
2022-06-21  9:02 ` rguenth at gcc dot gnu.org
2022-06-21  9:12 ` jakub at gcc dot gnu.org
2022-06-21  9:26 ` rguenther at suse dot de
2022-06-21  9:29 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-22  6:19 ` luoxhu at gcc dot gnu.org
2022-06-27 13:58 ` marxin at gcc dot gnu.org
2022-07-01  2:06 ` luoxhu at gcc dot gnu.org
2022-07-08 10:46 ` marxin at gcc dot gnu.org
2023-06-26  6:43 ` b.buschinski at googlemail dot com

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=bug-105740-4-PeJyhbZ0iF@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).