Package: kmc / 3.2.1+dfsg-1

Metadata

Package Version Patches format
kmc 3.2.1+dfsg-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
use shared libs | (download)

Makefile | 16 0 + 16 - 0 !
kmc_core/fastq_reader.h | 4 2 + 2 - 0 !
kmc_tools/fastq_reader.h | 6 3 + 3 - 0 !
3 files changed, 5 insertions(+), 21 deletions(-)

 use-shared-libs
makefile.patch | (download)

Makefile | 33 16 + 17 - 0 !
1 file changed, 16 insertions(+), 17 deletions(-)

 hardening
0005 Add static library target to makefile.patch | (download)

Makefile | 7 6 + 1 - 0 !
1 file changed, 6 insertions(+), 1 deletion(-)

 add static library target to makefile
disable python bindings.patch | (download)

Makefile | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 disable python3 bindings for the moment
 In a second time, this patch might be removed to take advantage of the newer
 python3 bindings coming with kmc 3, but let's disable them for the moment.
spelling.patch | (download)

kmc_tools/kmc2_db_reader.h | 4 2 + 2 - 0 !
kmc_tools/parameters_parser.cpp | 14 7 + 7 - 0 !
kmc_tools/parser.cpp | 6 3 + 3 - 0 !
3 files changed, 12 insertions(+), 12 deletions(-)

 spelling patch
simde | (download)

Makefile | 10 10 + 0 - 0 !
kmc_core/cpu_info.cpp | 8 7 + 1 - 0 !
kmc_core/intr_copy.h | 10 5 + 5 - 0 !
kmc_core/kmc.h | 2 2 + 0 - 0 !
kmc_core/raduls.h | 4 3 + 1 - 0 !
kmc_core/raduls_impl.h | 4 2 + 2 - 0 !
kmc_core/splitter.cpp | 6 3 + 3 - 0 !
7 files changed, 32 insertions(+), 12 deletions(-)

 support non-x86 systems via libsimde-dev

support mixed march.patch | (download)

kmc_core/raduls_avx.cpp | 3 3 + 0 - 0 !
kmc_core/raduls_impl.h | 8 8 + 0 - 0 !
kmc_core/raduls_sse2.cpp | 9 9 + 0 - 0 !
kmc_core/raduls_sse41.cpp | 6 6 + 0 - 0 !
4 files changed, 26 insertions(+)

 support mixed machine capabilities without impeding the build
 This allows one to build the package with almost any combination of machine
 capabilities.  The initial issue was reported against -march=x64-64-v2, but
 the present patch extends to v3, and probably any combination thrown by a
 -march=native.  The issue seems tied to the way the build process is modified
 by debian, so may not be very relevant cherry picked upstream.
 .
 Diagnostics information is kept around just in case, for convenience.