[pkg-go] Bug#1002227: Move to templexxx-xorsimd? (Was: Bug#1002227: golang-github-templexxx-xor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor returned exit code 1)

Nilesh Patra nilesh at debian.org
Wed Aug 3 19:52:21 BST 2022


This bug is causing and has caused autoremovals unfortunately. Taking a look
at upstream, this seems abandoned and upstream moved to xorsimd[1]
instead.

On brief testing, tests seem to pass for new package and botht the reverse-deps
for templexxx-xor have also migrated to new package in later upstream releases.

I tried taking a look at what is wrong with the tests currently - and my hunch is
XORPD might be causing some sort of unaligned mem access, however I don't have
skills in x86 assembly and do not know how to fix this.

And so I wonder if we could we move to the newer xorsimd package?

[1]: https://github.com/templexxx/xorsimd

On Fri, 24 Jun 2022 17:12:36 +0200 Lucas Nussbaum <lucas at debian.org> wrote:
> > > >  debian/rules build
> > > > dh build --buildsystem=golang --with=golang
> > > >    dh_update_autotools_config -O--buildsystem=golang
> > > >    dh_autoreconf -O--buildsystem=golang
> > > >    dh_auto_configure -O--buildsystem=golang
> > > >    dh_auto_build -O--buildsystem=golang
> > > >       cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 github.com/templexxx/xor
> > > > internal/goexperiment
> > > > internal/abi
> > > > github.com/templexxx/cpufeat
> > > > internal/cpu
> > > > runtime/internal/atomic
> > > > runtime/internal/sys
> > > > runtime/internal/math
> > > > internal/bytealg
> > > > runtime
> > > > github.com/templexxx/xor
> > > >    dh_auto_test -O--buildsystem=golang
> > > >       cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor
> > > > === RUN   TestVerifyBytesNoSIMD
> > > > --- PASS: TestVerifyBytesNoSIMD (1.13s)
> > > > === RUN   TestVerifyBytes
> > > > --- PASS: TestVerifyBytes (1.13s)
> > > > === RUN   TestVerifyBytesSrc1
> > > > unexpected fault address 0x0
> > > > fatal error: fault
> > > > [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x4e7234]
> > > >
> > > > goroutine 10 [running]:
> > > > runtime.throw({0x511356, 0xc00001a2d0})
> > > >       /usr/lib/go-1.17/src/runtime/panic.go:1198 +0x71 fp=0xc000033638 sp=0xc000033608 pc=0x433f11
> > > > runtime.sigpanic()
> > > >       /usr/lib/go-1.17/src/runtime/signal_unix.go:742 +0x2f6 fp=0xc000033688 sp=0xc000033638 pc=0x448696
> > > > github.com/templexxx/xor.xorSrc0({0xc00001a288, 0x11, 0x11}, {0xc00001a2a0, 0x11, 0x11}, {0xc00001a2b8, 0x11, 0x11})
> > > >       /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/templexxx/xor/sse2_amd64.s:43 +0x34 fp=0xc000033690 sp=0xc000033688 pc=0x4e7234


-- 
Best,
Nilesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20220804/642fc712/attachment.sig>


More information about the Pkg-go-maintainers mailing list