public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: Cygwin Apps <cygwin-apps@cygwin.com>
Subject: Re: [ITP] xxhash 0.7.4-1
Date: Tue, 14 Jul 2020 13:51:15 -0600	[thread overview]
Message-ID: <CAJ1FpuNxKZod0Qbu2EeX2pgvrBNqwf8haLmW7C9bm1bCQndYVA@mail.gmail.com> (raw)
In-Reply-To: <87365unjpk.fsf@Otto.invalid>

On Tue, 14 Jul 2020 at 10:29, ASSI <> wrote:
>
> ASSI writes:
> > By patching the Makefile, just like you need to do for all the other
> > stuff from the same author.  You can have a look at the zstd packages.
>
> Come to think of it, xxhash is already part of zstd.  Can't you just
> link to that?
>
>
> Regards,
> Achim.

I have patched the Makefile as suggested. The newest version of the
dist files as located at

https://github.com/djhenderson/Temp/raw/master/xxhash.zip

I compared the xxhash sources between the xxhash repo and the zstd
repo. There are major differences in the code. This is obvious from wc

$ wc -l /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.c
/usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.c
   43 /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.c
  864 /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.c
  907 total

$ wc -l /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.h
/usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.h
 2076 /usr/src/xxhash.src/xxhash-0.7.4-1.x86_64/origsrc/xxHash-0.7.4/xxhash.h
  285 /usr/src/zstd-1.4.5-1.src/zstd-1.4.5-1.x86_64/origsrc/zstd-1.4.5/lib/common/xxhash.h
 2361 total

I had a brief look at the code, but did not attempt to judge the
merits of either code base.

The zstd repo does not include the xxhsum command which has a similar
CLI to cksum, md5sum, sha256sum, etc.

Apparently xxhash will use the SSE2 instructions for some operations.
Someone with an older CPU without those instructions should test to
make sure the xxhsum programs works for them. (I'm just saying that, I
don't really know what that means.)

Any way, I would like some critical feedback on the dist packaging.

Thanks,
Doug
-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

  reply	other threads:[~2020-07-14 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 22:09 Doug Henderson
2020-07-14  4:42 ` ASSI
2020-07-14 16:29   ` ASSI
2020-07-14 19:51     ` Doug Henderson [this message]
2020-07-14 21:57       ` Ben RUBSON
2020-08-02 10:41         ` Ben RUBSON
2020-08-03  3:36           ` Doug Henderson
2020-08-03  5:58       ` Marco Atzeri
2020-08-03 16:08         ` Marco Atzeri
2020-08-25 15:46           ` Ben RUBSON

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=CAJ1FpuNxKZod0Qbu2EeX2pgvrBNqwf8haLmW7C9bm1bCQndYVA@mail.gmail.com \
    --to=djndnbvg@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /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).