[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

kmc update and options to move forward


I recently uploaded kmc 2.3+dfsg-10 to address #954270.  I'm not
very satisfied with my patch however, as it is a mere cap of the
default threading value, while waiting for a cleaner fix, which
exists and it is kind of frustrating.  :(

During my investigations to solve this bug, I found out upstream
went on with newer versions[1] (this was not caught by d/watch,
but I appended a fix here as well).  It turns out that someone
else had the freeze issue[2], and this newer version fixes the
threading issue appropriately.

[1] https://github.com/refresh-bio/KMC/releases
[2] https://github.com/refresh-bio/KMC/issues/82

The current kmc 2.3 benefits from wide architecture support, but
kmc 3.1.1 comes with highly optimized use of intrinsics, and CPU
extensions runtime detection.  This makes it very fast on recent
x86_64, but unsuitable on any other architecture, as is.

I thought about integrating SIMDe, but for the moment, I failed
at it.  I'm not entirely certain SIMDe will deal well with the
existing runtime detection within the code either.  Also, I'm
not very good at C++ (I learned C first unfortunately), so maybe
I just missed my point when trying to integrate SIMDe.  If
someone else is more at ease with SIMDe integration, maybe kmc
3.1.1 would be up to multiple architectures support that way ?

Otherwise, there is a bug open about lack of Aarch64 support[3],
but no answer for the moment.  I would prefer not to resort to
architecture removal without good reasons, but that would remain
a last resort option I guess.

[3] https://github.com/refresh-bio/KMC/issues/154

Kind Regards,
Étienne Mollier <etienne.mollier@mailoo.org>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/6, please excuse my verbosity.

Attachment: signature.asc
Description: PGP signature

Reply to: