public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107342] New: Optimization opportunity where integer '/' corresponds to '>>'
Date: Fri, 21 Oct 2022 08:36:48 +0000	[thread overview]
Message-ID: <bug-107342-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107342
           Summary: Optimization opportunity where integer '/' corresponds
                    to '>>'
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: aldyh at gcc dot gnu.org, amacleod at redhat dot com
  Target Milestone: ---

Created attachment 53742
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53742&action=edit
variant of 'gcc.dg/tree-ssa/pr107195-3.c'

Discovered during work on "Add 'gcc.dg/tree-ssa/pr107195-3.c' [PR107195]"
(which is pending approval for push to master branch) an optimization
opportunity where integer '/' corresponds to '>>'.  See discussion in
<https://inbox.sourceware.org/gcc-patches/CAGm3qMV5_7hEED6_NKNAFaiE5dFXapsrRGEd_MAqNiSsF15nmw@mail.gmail.com>
about 'f4b'/'foo4b', and the "variant of 'gcc.dg/tree-ssa/pr107195-3.c'"
attached here.

             reply	other threads:[~2022-10-21  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:36 tschwinge at gcc dot gnu.org [this message]
2022-10-21 19:04 ` [Bug tree-optimization/107342] " aldyh at gcc dot gnu.org
2022-10-21 19:10 ` aldyh at gcc dot gnu.org
2022-10-22 18:01 ` aldyh at gcc dot gnu.org
2022-11-04 14:18 ` cvs-commit at gcc dot gnu.org
2022-11-04 14:20 ` aldyh at gcc dot gnu.org
2022-11-28 22:13 ` 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-107342-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: 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).