notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
FreshPorts needs to find a new hosting provide willing to take a 2U chassis and host it free of charge. This is part of the FreshPorts project. Preferably in the Austin area. This is not a primary server, but it used for development.
non port: benchmarks/smhasher/distinfo

Number of commits found: 3

Tue, 3 Dec 2019
[ 09:59 pkubaj search for other commits by this committer ] Original commit   Revision:518923
benchmarks/smhasher: fix build on powerpc64

Inclusion of sys/endian.h and macros for bswap_32 and bswap_64 are necessary.
Other platforms do the same.

PR:		242323
Approved by:	gnn (maintainer), mentors (implicit approval)
Differential Revision:
Tue, 28 Apr 2015
[ 18:44 bdrewery search for other commits by this committer ] Original commit   Revision:384932 (Only the first 10 of 41 ports in this commit are shown above. View all ports for this commit)
USE_GITHUB: For the new support, fix DISTNAME to be more consistent.

When using GH_TAGNAME the DISTNAME would have GH_PROJECT and GH_ACCOUNT in
it. When not using GH_TAGNAME it would not have this. Now both cases
will add in the GH_PROJECT and GH_ACCOUNT.

Add special care to ensure that the DISTVERSION is not added in twice. If
a port does GH_TAGNAME=v${PORTVERSION} it will be added in twice though. For
that case DISTVERSIONPREFIX=v should be set and no GH_TAGNAME should be used.

empty() is used rather than (!defined || !${}) to support fmake.

The purpose of setting DISTNAME at all in these cases is to make it more clear
that the distfile is from *GITHUB* and to avoid collisions if a project were
to be renamed or moved. Without adding in GH_PROJECT and GH_ACCOUNT then there
are real risks that collisions on filenames would happen on renamed or moved
projects, which is fairly common. A GITHUB-generated file may not match
a custom-rolled or git-archive-rolled distfile.

PR:		199069
With hat:	portmgr
Testing done:	All USE_GITHUB ports without GH_COMMIT were
checksum/fetch/extract/WRKSRC tested.
Tue, 31 Mar 2015
[ 20:25 gnn search for other commits by this committer ] Original commit   Revision:382863
Add SMHasher hashing benchmark and test system as a new port.

SMHasher is a test suite designed to test the distribution, collision,
and performance properties of non-cryptographic hash functions -
it aims to be the "DieHarder" of hash testing, and does a pretty
good job of finding flaws with a number of popular hashes.

The SMHasher suite also includes MurmurHash3, which is the latest
version in the series of MurmurHash functions - the new version is
faster, more robust, and its variants can produce 32- and 128-bit
hash values efficiently on both x86 and x64 platforms.

Number of commits found: 3