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/107052] Range of __builtin_popcount can be improved with nonzerobits
Date: Wed, 05 Oct 2022 12:22:52 +0000	[thread overview]
Message-ID: <bug-107052-4-yQUgIYpGP0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107052-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:

https://gcc.gnu.org/g:ae56d600d223e996054483d7d7033ec8e258d39d

commit r13-3085-gae56d600d223e996054483d7d7033ec8e258d39d
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Oct 4 17:03:54 2022 +0200

    [PR tree-optimization/107052] range-ops: Pass nonzero masks through cast.

    Track nonzero masks through a cast in range-ops.

            PR tree-optimization/107052

    gcc/ChangeLog:

            * range-op.cc (operator_cast::fold_range): Set nonzero mask.

  parent reply	other threads:[~2022-10-05 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 15:18 [Bug tree-optimization/107052] New: " pinskia at gcc dot gnu.org
2022-09-27 15:18 ` [Bug tree-optimization/107052] " pinskia at gcc dot gnu.org
2022-09-27 15:24 ` pinskia at gcc dot gnu.org
2022-09-27 15:33 ` aldyh at gcc dot gnu.org
2022-09-27 15:36 ` pinskia at gcc dot gnu.org
2022-09-27 15:54 ` aldyh at gcc dot gnu.org
2022-09-27 16:22 ` aldyh at gcc dot gnu.org
2022-10-05 12:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-05 12:22 ` cvs-commit at gcc dot gnu.org
2022-10-05 12:23 ` aldyh 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-107052-4-yQUgIYpGP0@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).