Re: [Help] Could someone please have a look at gmap build failure

2023-07-19 Thread César Pomar
Hi, Technically, it is not a build failure. The build works, but the process is aborted due to a test failure. There is something wrong in the source code, which causes the test to not pass. In the best-case scenario, it's a bug that only affects non-x86 platforms, and in the worst-case scenario,

Re: [Help] Could someone please have a look at gmap build failure

2023-07-19 Thread Michael R. Crusoe
Hey César, Can you look at the build failures for non-x86? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041451 https://buildd.debian.org/status/fetch.php?pkg=gmap=arm64=2023-06-01%2Bds-1=1689254473=0 Note: /<>/build/src/gmap.nosimd does not exist. For faster speed, may want to compile

Re: [Help] Could someone please have a look at gmap build failure

2023-07-17 Thread César Pomar
Hi Andreas, It's a pleasure to be involved. If there's anything pending that I can assist with, please let me know. Best regards, César El jue, 13 jul 2023 a las 14:16, Andreas Tille () escribió: > Hi César, > > Am Thu, Jul 13, 2023 at 09:49:03AM +0200 schrieb César Pomar: > > I can also take

Re: [Help] Could someone please have a look at gmap build failure

2023-07-13 Thread Andreas Tille
Hi César, Am Thu, Jul 13, 2023 at 09:49:03AM +0200 schrieb César Pomar: > I can also take a look. ... Thanks a lot for becoming involved Andreas. -- http://fam-tille.de

Re: [Help] Could someone please have a look at gmap build failure

2023-07-13 Thread Michael R. Crusoe
Here is my fix https://salsa.debian.org/med-team/gmap/-/commit/596beba027da3944b0f45a9ffc9e03d1d9dca5ba On Thu, Jul 13, 2023 at 11:15 AM Michael R. Crusoe < michael.r.cru...@gmail.com> wrote: > Thanks César; I've done much of this already. I'll push my changes shortly > (testing the AVX512 level

Re: [Help] Could someone please have a look at gmap build failure

2023-07-13 Thread Michael R. Crusoe
Thanks César; I've done much of this already. I'll push my changes shortly (testing the AVX512 level now) On Thu, Jul 13, 2023 at 9:49 AM César Pomar wrote: > Hi, > > I think the same way. The code has multiple levels of vector extensions: > SSE2, SSE3, AVX... AVX512. The code has macros to

Re: [Help] Could someone please have a look at gmap build failure

2023-07-13 Thread César Pomar
Hi, I think the same way. The code has multiple levels of vector extensions: SSE2, SSE3, AVX... AVX512. The code has macros to define the data types according to the selected extension. It's very possible that they focused on SSE3 or AVX (which are already the minimum supported by any machine)

Re: [Help] Could someone please have a look at gmap build failure

2023-07-13 Thread Michael R. Crusoe
The real error is at gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -DTARGET=\"x86_64-pc-linux-gnu\" -DGMAPDB=\"/var/cache/gmap\" -DGSNAP=1 -mpopcnt -DHAVE_SSE2=1 -msse2 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-avx2 -g -O2

[Help] Could someone please have a look at gmap build failure

2023-07-12 Thread Andreas Tille
Hi, I admit I'm bad in such hardware internals that seem to break the build of gmap: intersect-uint2.c:409:21: error: incompatible types when initializing type '__m128i' using type 'int' 409 | __m128i p = _mm_shuffle_epi8(v_a, * (__m128i *) &(shuffle_mask16[r*16])); |