From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Aldy Hernandez <aldyh@redhat.com>,
GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Rename nonzero_bits to known_zero_bits.
Date: Fri, 21 Oct 2022 18:54:32 +0200 [thread overview]
Message-ID: <Y1LOyNwmFqzdjvRb@tucnak> (raw)
In-Reply-To: <Y1LOBd5mLy+7CQ4+@tucnak>
On Fri, Oct 21, 2022 at 06:51:19PM +0200, Jakub Jelinek wrote:
> Agreed.
>
> I think maybe_nonzero_bits would be fine.
Or yet another option is to change what we track and instead of
having just one bitmask have 2 as tree-ssa-ccp.cc does,
one bitmask says which bits are known to be always the same
and the other which specifies the values of those bits.
"For X with a CONSTANT lattice value X & ~mask == value & ~mask. The
zero bits in the mask cover constant values. The ones mean no
information."
Jakub
next prev parent reply other threads:[~2022-10-21 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 13:14 Aldy Hernandez
2022-10-21 16:45 ` Segher Boessenkool
2022-10-21 16:51 ` Jakub Jelinek
2022-10-21 16:54 ` Jakub Jelinek [this message]
2022-10-21 18:00 ` Segher Boessenkool
2022-11-01 16:33 ` Aldy Hernandez
2022-10-21 17:44 ` Segher Boessenkool
2022-10-24 7:21 ` Richard Biener
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=Y1LOyNwmFqzdjvRb@tucnak \
--to=jakub@redhat.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).