public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100958] New: two_value_replacement should move to match.pd Date: Tue, 08 Jun 2021 06:42:23 +0000 [thread overview] Message-ID: <bug-100958-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100958 Bug ID: 100958 Summary: two_value_replacement should move to match.pd Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: enhancement Priority: P3 Component: tree-optimization Assignee: pinskia at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- two_value_replacement can be fully implemented in match.pd now. So it should move. I did not do it originally but it. Comment from two_value_replacement : /* Optimize # x_5 in range [cst1, cst2] where cst2 = cst1 + 1 if (x_5 op cstN) # where op is == or != and N is 1 or 2 goto bb3; else goto bb4; bb3: bb4: # r_6 = PHI<cst3(2), cst4(3)> # where cst3 == cst4 + 1 or cst4 == cst3 + 1 to r_6 = x_5 + (min (cst3, cst4) - cst1) or r_6 = (min (cst3, cst4) + cst1) - x_5 depending on op, N and which of cst3 and cst4 is smaller. */
next reply other threads:[~2021-06-08 6:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 6:42 pinskia at gcc dot gnu.org [this message] 2021-06-08 6:42 ` [Bug tree-optimization/100958] " pinskia at gcc dot gnu.org 2023-04-09 17:21 ` pinskia at gcc dot gnu.org 2023-04-26 3:01 ` pinskia at gcc dot gnu.org 2023-04-28 14:27 ` cvs-commit at gcc dot gnu.org 2023-04-28 14:50 ` 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-100958-4@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).