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/106677] Abstraction overhead with std::views::join Date: Fri, 25 Aug 2023 18:34:20 +0000 [thread overview] Message-ID: <bug-106677-4-zNNUuPwwdk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106677-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106677 --- Comment #6 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:d9a0d692ffc6951c5670f54c3f4f17ec64a58600 commit r14-3486-gd9a0d692ffc6951c5670f54c3f4f17ec64a58600 Author: Andrew Pinski <apinski@marvell.com> Date: Sat Aug 19 15:30:45 2023 -0700 MATCH: Move `a ? one_zero : one_zero` matching after min/max matching In PR 106677, I noticed that on the trunk we were producing: ``` _25 = SR.116_117 == 0; _27 = (unsigned char) _25; _32 = _27 | SR.116_117; ``` From `SR.115_117 != 0 ? SR.115_117 : 1` Rather than: ``` _119 = MAX_EXPR <1, SR.115_117>; ``` Or (rather) ``` _119 = SR.115_117 | 1; ``` Due to the order of the patterns. Committed as approved with the new comment and testcase. Bootstrapped and tested on x86_64-linux-gnu with no regressions. gcc/ChangeLog: * match.pd (`a ? one_zero : one_zero`): Move below detection of minmax. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/phi-opt-34.c: New test.
prev parent reply other threads:[~2023-08-25 18:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106677-4@http.gcc.gnu.org/bugzilla/> 2023-05-06 21:03 ` pinskia at gcc dot gnu.org 2023-08-19 22:03 ` pinskia at gcc dot gnu.org 2023-08-24 23:39 ` pinskia at gcc dot gnu.org 2023-08-25 16:36 ` cvs-commit at gcc dot gnu.org 2023-08-25 18:34 ` cvs-commit at gcc dot gnu.org [this message]
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-106677-4-zNNUuPwwdk@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: linkBe 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).