• R/O
  • HTTP
  • SSH
  • HTTPS

List of commits

Tags
No Tags

Frequently used words (click to add to your profile)

javac++androidlinuxc#windowsobjective-ccocoa誰得qtpythonphprubygameguibathyscaphec計画中(planning stage)翻訳omegatframeworktwitterdomtestvb.netdirectxゲームエンジンbtronarduinopreviewer

blake3パッケージ


RSS
Rev. Time Author
ba468fb 2020-04-29 00:04:29 Jack O'Connor

build b3sum binaries in CI for new tags

These configs and code are adapted from the CI workflow in
https://github.com/oconnor663/blake3-py, especially the
upload_github_release_asset.py script, which is copied verbatim.

9b3dc0e 2020-04-17 12:57:30 dyknon

update debian/changelog

fcb4b83 2020-04-14 14:13:38 Jack O'Connor

version 0.3.2

Changes since 0.3.1:
- Fixed a compiler error on older versions of Clang,
https://github.com/BLAKE3-team/BLAKE3/issues/79.

d5e2653 2020-04-14 09:46:42 Jack O'Connor

refactor build.rs

Two main changes:
- In https://github.com/BLAKE3-team/BLAKE3/issues/79 we learned that
older versions of Clang require AVX-512 flags even to compile AVX-512
assembly.
- If the C compiler doesn't support AVX-512, we'd still prefer to build
the SSE4.1 and AVX2 assembly implementations, on x86_64.

6748b1b deb/0.3.1-3 2020-04-13 05:48:26 dyknon

delete unused patchs, update changelog

ff2b3e2 2020-04-13 05:43:40 dyknon

improve compatibility with gnu coreutils md5sum

* add --check and --quiet options
* read stdin when - is given

7ef795d 2020-04-12 19:38:11 Samuel Neves

Do not require AVX512DQ

Whereas vinserti64x4 is present on AVX512F, vinserti32x8 requires
AVX512DQ, which we do not test for. At this point there is not
much risk of incompatibility, since Skylake-X chips have all the
requires instruction sets, but let's be precise about this.

370ba36 2020-04-12 12:03:32 Jack O'Connor

print the compiler version in CI, for help with debugging

86c3174 2020-04-11 00:24:39 Jack O'Connor

unbreak neon benchmarks

A helper function was incorrectly restricted to x86-only. CI doesn't
currently cover this, because benchmarks are nightly-only, and it's kind
of inconvenient to set RUSTC_BOOTSTRAP=1 through `cross` (which normally
doesn't propagate env vars). But maybe we should start...

63217de deb/0.3.1-2 2020-04-10 08:24:01 dyknon

add debian/b3sum.manpages

b25d3b3 2020-04-10 08:12:57 dyknon

edit document installation

9b42172 2020-04-10 07:51:23 dyknon

add manpages

23ab9ed deb/0.3.1-1 2020-04-08 09:25:53 dyknon

gbp.conf

7c34929 2020-04-08 08:52:42 dyknon

patches

40f09b5 2020-04-08 08:51:41 dyknon

disable auto check + fix install error

11f711d 2020-04-08 07:56:45 dyknon

update debian files

ac06f04 2020-04-08 07:40:35 dyknon

update debian files

74ebc13 2020-04-04 04:34:13 dyknon

add debian files

b8d0d58 2020-04-03 16:34:19 dyknon

pristine-tar data for blake3_0.3.1.orig.tar.gz

019e870 upstream/0.3.1 2020-04-03 16:24:55 dyknon

New upstream version 0.3.1

e3069da 2020-04-02 23:23:46 Jack O'Connor

only run CI on branches and PRs, not tags

5e82396 2020-04-02 23:08:47 Jack O'Connor

version 0.3.1

Changes since 0.3.0:
- The x86 build now automatically falls back to "pure" Rust intrinsics,
under either of two possible conditions:
1. The `cc` crate fails to invoke a C compiler at all, indicating that
nothing of the right name (e.g. "cc" or "$CC" on Unix) is installed.
2. The `cc` crate detects that the compiler doesn't support AVX-512
flags, usually because it's too old.
The end result should be that most callers successfully build the
assembly implementations, and that callers who can't build those see a
warning but not an error. (And note that Cargo suppresses warnings for
non-path depencies.)

b8cdcb1 2020-04-02 08:13:15 Jack O'Connor

automatically fall back to the pure Rust build

There are two scenarios where compiling AVX-512 C or assembly code might
not work:

1. There might not be a C compiler installed at all. Most commonly this
is either in cross-compiling situations, or with the Windows GNU
target.
2. The installed C compiler might not support e.g. -mavx512f, because
it's too old.

In both of these cases, print a relevant warning, and then automatically
fall back to using the pure Rust intrinsics build.

Note that this only affects x86 targets. Other targets always use pure
Rust, unless the "neon" feature is enabled.

eec458d 2020-04-01 05:21:08 Samuel Neves

move prototypes to shared header file, and make all local functions static.

2dff29c 2020-04-01 05:02:57 Jack O'Connor

turn all compiler warnings into errors in CI

27f3273 2020-03-30 23:13:41 Jack O'Connor

put the CI badge back down in the README

6fbc1a6 2020-03-30 13:36:13 Jack O'Connor

version 0.3.0

Changes since version 0.2.3:
- The optimized assembly implementations are now built by default. They
perform better than the intrinsics implementations, and they compile
much more quickly. Bringing the default behavior in line with reported
benchmark figures should also simplify things for people running their
own benchmarks. Previously this crate only built Rust intrinsics
implementations by default, and the assembly implementations were
gated by the (slightly confusingly named) "c" feature. Now the "c"
feature is gone, and applications that need the old behavior can use
the new "pure" feature. Mainly this will be applications that don't
want to require a C compiler. Note that the `b3sum` crate previously
activated the "c" feature by default, so its behavior hasn't changed.

1527405 2020-03-30 12:12:47 Jack O'Connor

add testing-only flags to disable individual instruction sets

This lets CI test a wider range of possible SIMD support settings.

e06a0f2 2020-03-30 07:02:03 Jack O'Connor

refactor the Cargo feature set

The biggest change here is that assembly implementations are enabled by
default.

Added features:
- "pure" (Pure Rust, with no C or assembly implementations.)

Removed features:
- "c" (Now basically the default.)

Renamed features;
- "c_prefer_intrinsics" -> "prefer_intrinsics"
- "c_neon" -> "neon"

Unchanged:
- "rayon"
- "std" (Still the only feature on by default.)

7caf1ad 2020-03-29 14:44:00 Jack O'Connor

version 0.2.3

Changes since version 0.2.2:
- Bug fix: Commit 13556be fixes a crash on Windows when using the SSE4.1
assembly implementation (--features=c, set by default for b3sum). This
is undefined behavior and therefore a potential security issue.
- b3sum now supports the --num-threads flag.
- The C API now includes a blake3_hasher_finalize_seek() function, which
returns output from any position in the extended output stream.
- Build fix: Commit 5fad419 fixes a compiler error in the AVX-512 C
intrinsics implementation targeting the Windows GNU ABI.