From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: 7zip-22.00
Date: Mon, 18 Jul 2022 22:46:08 +0200 [thread overview]
Message-ID: <20220718204608.Z8uXgxQqxdZEwLIiW_FPM4BsOFk5PxGwOLH5k5i6F7s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37940@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
New comment by r-ricci on void-packages repository
https://github.com/void-linux/void-packages/pull/37940#issuecomment-1188292968
Comment:
> What are the portion written in assembly and what ISA extensions do they use?
The readme says:
```
Asm - Source code in Assembler : optimized code for CRC, SHA, AES, LZMA decoding.
```
The changelog contains this entry:
```
- Asm\x86\LzmaDecOpt.asm: new optimized LZMA decoder written in asm
for x64 with about 30% higher speed than main version of LZMA decoder written in C.
```
so the performance improvement is significant (but I didn't run benchmarks on my own).
The documentation doesn't state what ISA extensions are used, so you have to read the files in the Asm subdirectory.
There are e.g. some AVX extensions, which are not supported on all the CPUs Void supports, but there are also some `ifdef`s and I don't understand how the build system actually triggers them. I'll do some tests.
next prev parent reply other threads:[~2022-07-18 20:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 10:27 [PR PATCH] " r-ricci
2022-07-09 10:34 ` [PR PATCH] [Updated] " r-ricci
2022-07-10 18:15 ` r-ricci
2022-07-10 19:50 ` r-ricci
2022-07-10 22:11 ` r-ricci
2022-07-12 13:20 ` r-ricci
2022-07-12 13:23 ` r-ricci
2022-07-12 13:52 ` r-ricci
2022-07-12 14:47 ` r-ricci
2022-07-12 15:46 ` r-ricci
2022-07-13 9:04 ` [PR PATCH] [Updated] " r-ricci
2022-07-13 9:18 ` r-ricci
2022-07-13 9:43 ` [PR PATCH] [Updated] " r-ricci
2022-07-13 11:00 ` 0x5c
2022-07-13 12:13 ` r-ricci
2022-07-13 18:24 ` [PR PATCH] [Updated] " r-ricci
2022-07-13 18:25 ` r-ricci
2022-07-13 18:37 ` [PR PATCH] [Updated] " r-ricci
2022-07-13 18:40 ` r-ricci
2022-07-14 1:39 ` abenson
2022-07-14 12:45 ` r-ricci
2022-07-18 10:07 ` r-ricci
2022-07-18 17:40 ` 0x5c
2022-07-18 19:39 ` [PR PATCH] [Updated] " r-ricci
2022-07-18 20:46 ` r-ricci [this message]
2022-07-18 20:50 ` 0x5c
2022-07-18 20:51 ` r-ricci
2022-08-15 16:50 ` [PR PATCH] [Updated] " r-ricci
2022-08-15 17:23 ` r-ricci
2022-08-15 17:25 ` r-ricci
2022-08-15 17:26 ` [PR PATCH] [Updated] " r-ricci
2022-08-28 21:52 ` r-ricci
2022-08-28 21:52 ` [PR PATCH] [Updated] " r-ricci
2022-08-29 12:40 ` r-ricci
2022-08-29 12:53 ` [PR PATCH] [Updated] New package: 7zip-22.01 r-ricci
2022-08-29 12:58 ` r-ricci
2022-08-29 13:07 ` r-ricci
2022-08-29 13:40 ` [PR PATCH] [Updated] " r-ricci
2022-08-29 13:40 ` r-ricci
2022-08-29 17:11 ` [PR PATCH] [Updated] " r-ricci
2022-11-28 2:04 ` github-actions
2022-12-03 22:30 ` [PR PATCH] [Updated] " r-ricci
2022-12-03 22:38 ` r-ricci
2022-12-04 14:56 ` r-ricci
2022-12-17 17:54 ` r-ricci
2022-12-20 19:25 ` [PR PATCH] [Merged]: " leahneukirchen
2022-12-21 2:07 ` sgn
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=20220718204608.Z8uXgxQqxdZEwLIiW_FPM4BsOFk5PxGwOLH5k5i6F7s@z \
--to=r-ricci@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).