<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/lib/libzstd/Makefile, branch release/13.1.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=release%2F13.1.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=release%2F13.1.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2022-02-11T16:42:30Z</updated>
<entry>
<title>Disable clang 14 warning about bitwise operators in zstd</title>
<updated>2022-02-11T16:42:30Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2022-02-08T20:46:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=284434f7a6fcae8f2a151862aeb9be3bb668ca87'/>
<id>urn:sha1:284434f7a6fcae8f2a151862aeb9be3bb668ca87</id>
<content type='text'>
Parts of zstd, used in openzfs and other places, trigger a new clang 14
-Werror warning:

```
sys/contrib/zstd/lib/decompress/huf_decompress.c:889:25: error: use of bitwise '&amp;' with boolean operands [-Werror,-Wbitwise-instead-of-logical]
                        (BIT_reloadDStreamFast(&amp;bitD1) == BIT_DStream_unfinished)
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```

While the warning is benign, it should ideally be fixed upstream and
then vendor-imported, but for now silence it selectively.

MFC after:	3 days

(cherry picked from commit 5f2aca83940097d7d23b4137073fb601f8e74232)
</content>
</entry>
<entry>
<title>libprivatezstd: Restrict symbol visibility similar to upstream</title>
<updated>2021-01-03T19:26:46Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2021-01-03T19:26:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=98689d0ffb0a0e218d3b32201df59be9fa771830'/>
<id>urn:sha1:98689d0ffb0a0e218d3b32201df59be9fa771830</id>
<content type='text'>
We have to relax three symbols to dynamically link zstd(1), but the rest
are the same.
</content>
</entry>
<entry>
<title>pkgbase: Move libprivatezstd from utilities to runtime</title>
<updated>2020-11-12T14:04:08Z</updated>
<author>
<name>Emmanuel Vadot</name>
<email>manu@FreeBSD.org</email>
</author>
<published>2020-11-12T14:04:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6cd88fe0e03f5abee1792dff9272fb4e2e6d0e65'/>
<id>urn:sha1:6cd88fe0e03f5abee1792dff9272fb4e2e6d0e65</id>
<content type='text'>
libarchive depends on it by default and tar uses libarchive.
So on a update :
1/ runtime contain tar
2/ runtime have libarchive in shlibs_required
3/ libarchive packages depends on utilities
4/ utilities depends on runtime
5/ kaboom

All users of libprivatezstd (libarchive related stuff and objcopy/ar)
are already in utilities.

Discussed with: bapt
</content>
</entry>
<entry>
<title>Only set WARNS if not defined</title>
<updated>2020-09-11T13:28:37Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-09-11T13:28:37Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ecebb3cc1d2d074defc302d8ae6820bb6b20d4fe'/>
<id>urn:sha1:ecebb3cc1d2d074defc302d8ae6820bb6b20d4fe</id>
<content type='text'>
This would allow interested parties to do experimental runs with an
environment set appropriately to raise all the warnings throughout the
build; e.g. env WARNS=6 NO_WERROR=yes buildworld.

Not currently touching the numerous instances in ^/tools.

MFC after:	1 week
</content>
</entry>
<entry>
<title>Update to Zstandard 1.4.5</title>
<updated>2020-05-23T21:23:46Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2020-05-23T21:23:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=37f1f2684f2670b204080ef2d6c303becd28545f'/>
<id>urn:sha1:37f1f2684f2670b204080ef2d6c303becd28545f</id>
<content type='text'>
As usual, the full release notes are found on Github:

  https://github.com/facebook/zstd/releases/tag/v1.4.5

Notable changes include:

* Improved decompress performance on amd64 and arm (5-10%
  and 15-50%, respectively).
* '--patch-from' zstd(1) CLI option, which provides something like a very fast
  version of bspatch(1) with slightly worse compression.  See release notes.

In this update, I dropped the 3-year old -O0 workaround for an LLVM ARM bug;
the bug was fixed in LLVM SVN in 2017, but we didn't remove this workaround
from our tree until now.

MFC after:	I won't, but feel free
Relnotes:	yes
</content>
</entry>
<entry>
<title>Update to Zstandard 1.4.2</title>
<updated>2019-08-08T16:54:22Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2019-08-08T16:54:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4d3f1eafc9372600fc1e5472187846d07fe96c54'/>
<id>urn:sha1:4d3f1eafc9372600fc1e5472187846d07fe96c54</id>
<content type='text'>
The full release notes for 1.4.1 (skipped) and 1.4.2 can be found on Github:

  https://github.com/facebook/zstd/releases/tag/v1.4.1
  https://github.com/facebook/zstd/releases/tag/v1.4.2

These are mostly minor updates; 1.4.1 purportedly brings something like 7%
faster decompression speed.

Relnotes:	yes
</content>
</entry>
<entry>
<title>Update to Zstandard 1.3.8</title>
<updated>2018-12-29T21:18:01Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2018-12-29T21:18:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=a0483764f3d68669e9b7db074bcbd45b050166bb'/>
<id>urn:sha1:a0483764f3d68669e9b7db074bcbd45b050166bb</id>
<content type='text'>
This merge brings in a couple new files, which needed to be attached to the
build; a new dependency on &lt;limits.h&gt;, which must be stubbed; and a name
change in the Context parameter constants, from ZSTD_p_foo to ZSTD_c_foo.

Significantly, it fixes a kernel build error with GCC where floating-point
functions were included in the kernel build, by hiding them under the same
compile-time #ifdef that already covered their invocation.  That issue was
introduced to FreeBSD in the 1.3.7 update and tracked upstream here:

  https://github.com/facebook/zstd/issues/1386

The full 1.3.8 release notes can be found on Github:

  https://github.com/facebook/zstd/releases/tag/v1.3.8

Relnotes:	yes
</content>
</entry>
<entry>
<title>Update to Zstandard 1.3.7</title>
<updated>2018-10-22T18:29:12Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2018-10-22T18:29:12Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=0f743729abbfc5c9d78a713f72241a4d4bd601ec'/>
<id>urn:sha1:0f743729abbfc5c9d78a713f72241a4d4bd601ec</id>
<content type='text'>
Relnotes:	yes
Sponsored by:	Dell EMC Isilon
</content>
</entry>
<entry>
<title>lib(private)zstd: Fix riscv build</title>
<updated>2018-03-18T03:42:57Z</updated>
<author>
<name>Conrad Meyer</name>
<email>cem@FreeBSD.org</email>
</author>
<published>2018-03-18T03:42:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=22aec4de9f9ecb7a5e1b2a663d74692cdb4cf61a'/>
<id>urn:sha1:22aec4de9f9ecb7a5e1b2a663d74692cdb4cf61a</id>
<content type='text'>
Link __bswap[ds]i2() intrinsics in to libzstd for riscv, where the C runtime
apparently lacks such intrinsics.

Broken in r330894.

Reported by:	asomers
Sponsored by:	Dell EMC Isilon
</content>
</entry>
<entry>
<title>Addd work around for LLVM bug 35023.</title>
<updated>2017-11-26T16:41:30Z</updated>
<author>
<name>Michal Meloun</name>
<email>mmel@FreeBSD.org</email>
</author>
<published>2017-11-26T16:41:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=30347b77ccbd965fbc547cef0430eb893475b5ff'/>
<id>urn:sha1:30347b77ccbd965fbc547cef0430eb893475b5ff</id>
<content type='text'>
Clang crashes when compiling zstd_compress.c with optimization for ARM targets.
https://bugs.llvm.org/show_bug.cgi?id=35023
</content>
</entry>
</feed>
