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/68894] Recognition min/max pattern with multiple arguments.
Date: Mon, 24 Apr 2023 15:50:37 +0000	[thread overview]
Message-ID: <bug-68894-4-S5Wr0vyoGT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68894-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:7049241f6ee558cfc0b227b5a0a355ec29afd6f1

commit r14-201-g7049241f6ee558cfc0b227b5a0a355ec29afd6f1
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu Apr 20 10:56:17 2023 -0700

    PHIOPT: Allow other diamond uses when do_hoist_loads is true

    While working on adding diamond shaped form to match-and-simplify
    phiopt, I Noticed that we would not reach there if do_hoist_loads
    was true. In the original code before the cleanups it was not
    obvious why but after I finished the cleanups, it was just a matter
    of removing a continue and that is what this patch does.

    This just happens also to fix a bug report that I noticed too.

    OK? Bootstrapped and tested on x86_64-linux-gnu.

    gcc/ChangeLog:

            PR tree-optimization/68894
            * tree-ssa-phiopt.cc (tree_ssa_phiopt_worker): Remove the
            continue for the do_hoist_loads diamond case.

  parent reply	other threads:[~2023-04-24 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-68894-4@http.gcc.gnu.org/bugzilla/>
2023-04-09 23:33 ` pinskia at gcc dot gnu.org
2023-04-09 23:50 ` pinskia at gcc dot gnu.org
2023-04-10 22:11 ` pinskia at gcc dot gnu.org
2023-04-24 15:50 ` cvs-commit at gcc dot gnu.org [this message]
2023-04-24 15:57 ` pinskia at gcc dot gnu.org
2023-04-24 19:06 ` pinskia at gcc dot gnu.org
2023-04-28 14:55 ` pinskia at gcc dot gnu.org

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-68894-4-S5Wr0vyoGT@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).