Copy: zigo@debian.org
Copy: onovy@debian.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --UfFJwMSNM6zXiPoZlvG8KwDa4mFxEmWYO
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi Ondřej,

I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend support to other archs?

Actually, a -med team package fastp has started to depend on libisal-dev, and this
now is limited to the few archs isal supports. So it would be really nice if isal
can build on more archs.

Please do let me know.

Nilesh



--UfFJwMSNM6zXiPoZlvG8KwDa4mFxEmWYO--

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFqeqYFAwAAAAAACgkQALrnSzQzafGp Xw//dhkaVPt8zHVY5lBT4uuXm5p2qjH8m9sJs4AyQudLIGuDrdMwcFlP0SQobd1wCy78RPYng3mA wh77hnGMrE2x1//b97tau/TrHwkQPJuvAGvhfjlaso/D5U3iz521hZRL3yuVGNP80YQDeoNrq4DK skv/ztisxgS3hinxYuUItmyQL72B0Axbd1mBb1jgtyIq7LN4x0grqEIvbrZB2QigZI7uzrNX4Lao HLtrb/jdZbY3ha/9/0L6QtvKNR2DP/t+tyTZuPXamdettozfJl82sTrCj/IEO/5rIS6WijRxMkfD Nfg0A7h5UEWWRs0pMLqRVK5YU5FEuSi5UZ7wK6GtLyXV0xjxGc+HfhnqLRW9H+wFFhgsg8L9ime7 w4imnROkmBqZOcZTOzT8wZxSEUI47po3PSkoEluuYoRbxDxv/k0xNqwyHjQ0B//dZWyXkMtlPtQl lgaD7IgGupS7979ThE5KdgC9edop6d5faZthz5jtUwqdAxQ5eWq5bPwoblLrS6f0XvYKkRM5drJD BdV7DcZMmNF/4yYo7/A8wzoIdP9MRSY6yFI7EZhbfdsUnmLQ4pPKe7yN/A5tGwL7APwnOdh2/WAx Qr2eCsITDB0/zkSbwf2/nuxGg9uufI1JlV1bGb47Pwloth1G229SgO8pHB3w4chy/rhNhfUMkVao Jyk=
=2Euq
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/16/21 9:09 AM, Nilesh Patra wrote:

Hi Ondřej,

I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend
support to other archs?

Actually, a -med team package fastp has started to depend on
libisal-dev, and this
now is limited to the few archs isal supports. So it would be really
nice if isal
can build on more archs.

Please do let me know.

Nilesh

Hi,

Did you look into the source package? isal is written in assembly
language...

Cheers,

Thomas Goirand (zigo)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Did you look into the source package? isal is written in assembly
language...

That doesn't seem quite right.
The readme states:

other:

Compiler: Portable base functions are available that build with most C compilers.

And it does look like there are corresponding .c implementations, at
least for some of the functions.

Not sure about source or binary compatibility, though.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi

On Sat, 16 Oct 2021 at 10:42, Thomas Goirand <zigo@debian.org> wrote:

On 10/16/21 9:09 AM, Nilesh Patra wrote:

Hi Ondřej,

I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend
support to other archs?

Actually, a -med team package fastp has started to depend on
libisal-dev, and this
now is limited to the few archs isal supports. So it would be really
nice if isal
can build on more archs.

Please do let me know.

Nilesh

Hi,

Did you look into the source package? isal is written in assembly
language...

Cheers,

Thomas Goirand (zigo)

I see at least an erasure_code/ppc64le directory.

I did a quick test build in Ubuntu and the package built and passed
its tests on armhf, ppc64el and riscv64, failing only because of
missing symbols. Perhaps the reduced libisal2.symbols.arm64 can be
used for other architectures as well?

Regards
Graham

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

To: zigo@debian.org (Thomas Goirand)
Copy: debian-python@lists.debian.org (Debian Python)
Copy: onovy@debian.org
Copy: debian-med@lists.debian.org (Debian Med Project List)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --KmlioGUfHacJZeryVnI2iA9an1YqvODeS
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

On 10/16/21 4:07 PM, Graham Inggs wrote:

Hi,

Did you look into the source package? isal is written in assembly
language...

I see at least an erasure_code/ppc64le directory.

I did a quick test build in Ubuntu and the package built and passed
its tests on armhf, ppc64el and riscv64, failing only because of
missing symbols. Perhaps the reduced libisal2.symbols.arm64 can be
used for other architectures as well?

After Graham's tests, would it be possible to extend the arch list?
I could help test it across more archs if you would like -- porter boxes to rescue :)

Nilesh



--KmlioGUfHacJZeryVnI2iA9an1YqvODeS--

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmFsDeIFAwAAAAAACgkQALrnSzQzafFo tA//YiVx3kY6IGt/0ctUvH88k1L+hYZT2gj0OS+A4y/iePtzwFDgcFVI+TocsakWCNIyjirY475l pey7fu9ljJ9pTY9V1ZO1C2gEnjd9AGxQGCZ89WYx4S1KOJ1Rg5knSRxT/D+5LXM+KaKqBsEYuX/K bBL6CoKNTaW8X7PpbXguCB/r59pkA9aU7jCgZeuf3YA8kNakNoRne5bnJQdAgon7QW4AxzPJOBEe K/HViu1Iycddt5NE0ZqRk8gvhB8IyrtJOawRmSS7A0RLXMnFmnzN+U9f784eMsds5CkK9/nezjBA nXe6SXfk3bbnSLezxE55fVaA4HRDV+F7HzCdlWj87rVdrHO7+8iduaMbbzQdde0c5+LeyQZvOHj6 nu3xXlPKKdJeCZzjW0W4xR660jVkXBABHL3jZd8Hhh/Z82zxKv1qGBzECiRNwrJzQh9g4xleyv9G BqzNwByKBsHJWmtBN8Se7CAkOnFxo5ao+zSFztmwrQd/sobagQoRKa7zecRv0N4WNldKrxOiVsJz nU/JH3+bD1xV5kXOZvQPjkPSvnbZWFnG3c9czSpr4/U2wPgKDfpQyBdHbTEazrXnken2dLzFgUdE ZnnG9hr6Y2aFtpprs1AJ33AabFQbMVoR7ilSXjgyyYtLTtRvGaQGC60u5YT6b8S7G1tPCOWKa7uu DC8=
=DJAJ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Nilesh,

so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra <nilesh@nileshpatra.info> napsal:

I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend support
to other archs?

When I packed libisal, only "customer" was liberasurecode. Liberasurecode supports many backends and supports all archs. And because libisal is
highly optimized for ARM and amd64, I built it only for these archs. Other platforms are supported, but not optimized. liberasurecode directly should perform better.

Actually, a -med team package fastp has started to depend on libisal-dev


And because there is other "customer", I will try to build it for all
archs.

Thanks.

--
Best regards
Ondřej Nový

<div dir="ltr"><div>Hi Nilesh,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra &lt;<a href="mailto:nilesh@nileshpatra.info">nilesh@nileshpatra.info</a>&gt; napsal:</div><blockquote
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.<br>
Is there a particular reason for this? -- Is it possible to extend support to other archs?<br></blockquote><div><br></div><div>When I packed libisal, only &quot;customer&quot; was liberasurecode. Liberasurecode supports many backends and supports all
archs. And because libisal is highly optimized for ARM and amd64, I built it only for these archs. Other platforms are supported, but not optimized. liberasurecode directly should perform better.</div><div><br></div><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1