From: Jakub Jelinek <jakub@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: 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:51:17 +0200 [thread overview]
Message-ID: <Y1LOBd5mLy+7CQ4+@tucnak> (raw)
In-Reply-To: <20221021164533.GW25951@gate.crashing.org>
On Fri, Oct 21, 2022 at 11:45:33AM -0500, Segher Boessenkool wrote:
> On Fri, Oct 21, 2022 at 03:14:26PM +0200, Aldy Hernandez via Gcc-patches wrote:
> > The name nonzero_bits is confusing. We're not tracking nonzero bits.
> > We're tracking known-zero bits, or at the worst we're tracking "maye
> > nonzero bits". But really, the only thing we're sure about in the
> > "nonzero" bits are the bits that are zero, which are known to be 0.
> > We're not tracking nonzero bits.
>
> Indeed.
>
> > I know we've been carrying around this name forever, but the fact that
> > both of the maintainers of the code *HATE* it, should be telling.
> > Also, we'd also like to track known-one bits in the irange, so it's
> > best to keep the nomenclature consistent.
>
> And that as well.
>
> However:
>
> > * asan.cc (handle_builtin_alloca): Rename *nonzero* to *known_zero*.
>
> Our "nonzero" means "not known to be zero", not "known to be zero", so
> this renaming makes it worse than it was. Rename it to
Agreed.
I think maybe_nonzero_bits would be fine.
Anyway, the reason it is called this way is that we have similar APIs
on the RTL side, nonzero_bits* in rtlanal.cc.
So if we rename, it should be renamed consistently.
> "not_known_zero", make that a thin wrapper around a new "known_zero",
> and slowly get rid of not_known_zero?
Jakub
next prev parent reply other threads:[~2022-10-21 16:51 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 [this message]
2022-10-21 16:54 ` Jakub Jelinek
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=Y1LOBd5mLy+7CQ4+@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).