According to https://github.com/FFTW/fftw3/issues/182 , this looks like
no longer an issue. Please consider reverting Ubuntu-specific changes in
the next upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: fftw3 (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notifications about th
** Changed in: fftw3 (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notifications about this bu
** Bug watch added: Debian Bug tracker #943396
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943396
** Also affects: fftw3 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943396
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
We probably don't need to fix eoan too (?)
** Changed in: fftw3 (Ubuntu Eoan)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoa
This bug was fixed in the package fftw3 - 3.3.8-2ubuntu1
---
fftw3 (3.3.8-2ubuntu1) focal; urgency=medium
* debian/rules: Disable Neon for armhf single precision builds to avoid
crashes. It's unclear if this is an fftw3 internal bug in its code
generator (which fftw3 does by
Fix proposed to Debian:
https://salsa.debian.org/science-team/fftw3/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notific
There's an additional bug that's slowing me down right now:
If you run 'bench' under gdb or just compile the package using gcc-8
then 'bench' spins forever at 100% CPU never completing any tests.
I will try to avoid having to fix that bug here...
--
You received this bug notification because yo
** Changed in: fftw3 (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notifications abou
** Changed in: fftw3
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notifications about this bug go to:
https:
Also without Valgrind the above command does not crash at all on armhf
for me. So I'm now working on the theory this bug is a consequence of
the deb's custom build flags, which includes neon supporting the idea in
comment #3.
--
You received this bug notification because you are a member of Ubunt
When I build the native armhf tarball on armhf and then run the same
command I find many different bugs:
$ valgrind ./bench --verify ofr108*118
...
==27624== ERROR SUMMARY: 8257294 errors from 859 contexts (suppressed: 0 from 0)
This is why I was reluctant to use Valgrind. Because more often than
** Also affects: fftw3 via
https://github.com/FFTW/fftw3/issues/182
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan
Reported upstream on https://github.com/FFTW/fftw3/issues/182 , with
some luck they have an idea about the bug
** Bug watch added: github.com/FFTW/fftw3/issues #182
https://github.com/FFTW/fftw3/issues/182
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trying to debug a bit on a canonistack instance
==5906== Command: ./bench --verify ofr108*118
==5906==
==5906== Invalid write of size 8
==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876)
==5906==by 0x49174A8: ST (simd-neon.h:119)
==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230)
==5906==
persists:
https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17546506
** Changed in: fftw3 (Ubuntu Eoan)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
So far I can't reproduce any crash in the tests on armhf (or aarch64).
But I haven't tried everything yet...
In the meantime, can anyone reproduce the failure and produce a fresh
log? If so, can you verify for me which binary is crashing?
** Changed in: fftw3 (Ubuntu Eoan)
Status: In Progr
** Changed in: fftw3 (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843733
Title:
fftw3 ftbfs in eoan (armhf only)
To manage notifications abou
** Changed in: fftw3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: fftw3 (Ubuntu Eoan)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Confirmed
** Tags removed: rls-ee-incoming
--
You received this bug notification because you ar
19 matches
Mail list logo
