Cursory glance at `git diff v2.5.0..v2.51 **/**.h` tells me you didn't change anything
ABI-wise.
Cheers,
Marcus
On 14.02.22 13:38, Johannes Demel wrote:
Hi all,
while I did not run the ABI compliance checker to compare 2.5.0 vs 2.5.1 specifically, it
is simple and can be done with this
Hi all,
while I did not run the ABI compliance checker to compare 2.5.0 vs 2.5.1
specifically, it is simple and can be done with this tool:
https://lvc.github.io/abi-compliance-checker/#ABI_Dumper
So far, we were able to keep the ABI compatible across VOLK 2.x.
Also, we didn't change any
Fons - filesystem is used for the volk_profile utility.
Chris - do not assume ABI compatibility. A number of small things have
changed in ".h" files.
On Sat, Feb 12, 2022 at 6:19 PM Chris Vine wrote:
> On Sat, 12 Feb 2022 11:40:26 +0100
> Johannes Demel wrote:
> > Hi everyone!
> >
> > You can
On Sat, 12 Feb 2022 11:40:26 +0100
Johannes Demel wrote:
> Hi everyone!
>
> You can find the news at https://www.libvolk.org/release-v251.html as well.
>
> We have a new VOLK release! We are happy to announce VOLK v2.5.1! We
> want to thank all contributors. This release wouldn't have been
On Sat, Feb 12, 2022 at 11:40:26AM +0100, Johannes Demel wrote:
> In the past, we relied on Boost for several tasks in `volk_profile`. For
> years, we minimized Boost usage to `boost::filesystem`. We mostly switched
> to C++17 `std::filesystem` years ago. The last distribution in our CI system
>
Hi everyone!
You can find the news at https://www.libvolk.org/release-v251.html as well.
We have a new VOLK release! We are happy to announce VOLK v2.5.1! We
want to thank all contributors. This release wouldn't have been possible
without them.
The list of contributors is pretty long this
