From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22689@debbugs.gnu.org
Subject: bug#22689: [PATCH] Add logcount
Date: Sat, 30 Sep 2017 09:16:36 -0400 [thread overview]
Message-ID: <20170930131636.xe22lbwlea7yqelh@logos.localdomain> (raw)
In-Reply-To: <83mv5c4dl0.fsf@gnu.org>
On 30/09/17 at 02:42pm, Eli Zaretskii wrote:
> > +#if defined (__POPCNT__) && defined (__GNUC__) && (__GNUC__> 4 || (__GNUC__== 4 && __GNUC_MINOR__> 1))
> > +#define HAVE_BUILTIN_POPCOUNTLL
> > +#endif
>
> Where does __POPCNT__ definition come from? I don't see it in my
> GCC's "gcc -dM" output.
>
> As for the rest of the condition, I think you should use GNUC_PREREQ,
> like this:
>
> #if GNUC_PREREQ (4, 1, 0)
I guess it comes from nowhere, that condition and the two helper
functions come from here
https://rosettacode.org/wiki/Population_count#C
> > +static uint64_t
> > +bitcount64 (uint64_t b)
> > +{
> > + b -= (b >> 1) & 0x5555555555555555;
> > + b = (b & 0x3333333333333333) + ((b >> 2) & 0x3333333333333333);
> > + b = (b + (b >> 4)) & 0x0f0f0f0f0f0f0f0f;
> > + return (b * 0x0101010101010101) >> 56;
>
> Shouldn't these constants have a ULL suffix, to make sure they are not
> truncated to a 32-bit int?
Probably, I don't know--I'm out of my comfort zone here.
> > +#else /* HAVE_BUILTIN_POPCOUNTLL */
> > + if (XINT (value) <= UINT_MAX)
> > + XSETINT (res, bitcount32 (XUINT (value)));
> > + else if (XINT (value) <= ULONG_MAX)
> > + XSETINT (res, bitcount64 (XUINT (value)));
>
> The comparisons against Uxxx_MAX seem to assume that VALUE is
> unsigned, but that's not guaranteed, right?
True. Should I instead be doing
XINT (value) <= xxx_MAX &&
XINT (value) >= xxx_MIN
or might there be a better check? For negative values popcount
typically counts ones of the two's complement
next prev parent reply other threads:[~2017-09-30 13:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 23:18 bug#22689: 25.1.50; implement logcount Mark Oteiza
2017-09-29 17:41 ` bug#22689: [PATCH] Add logcount Mark Oteiza
2017-09-30 11:42 ` Eli Zaretskii
2017-09-30 13:16 ` Mark Oteiza [this message]
2017-09-30 13:59 ` Eli Zaretskii
2017-09-30 14:55 ` Mark Oteiza
2017-09-30 15:38 ` Eli Zaretskii
2017-09-30 16:03 ` Mark Oteiza
2017-09-30 16:17 ` Eli Zaretskii
2017-09-30 17:07 ` Mark Oteiza
2017-09-30 17:53 ` Eli Zaretskii
2017-09-30 18:18 ` Mark Oteiza
2017-09-30 16:50 ` Benjamin Riefenstahl
2017-09-30 16:59 ` Mark Oteiza
2017-09-30 22:48 ` Paul Eggert
2017-09-30 23:22 ` Mark Oteiza
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170930131636.xe22lbwlea7yqelh@logos.localdomain \
--to=mvoteiza@udel.edu \
--cc=22689@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).