Floating point exception on armhf and i386

[tillea]

Please report

• 2.3.3 Debian packaged
• Architecture: i386 and armhf
• There is a bug report from the Debian CI team covering only these two architectures.

Assembly error

The bug report links to the full build log where you dan find at the end:

abyss-rresolver-short  -b1G -j2 -k25  \
-h test-1-rr --dot -c test-1-rr.fa -g test-1-rr.dot test-1.fa test-1.dot test-data/reads1.fastq test-data/reads2.fastq 
make: *** [/usr/bin/abyss-pe:585: test-1-rr.dot] Floating point exception

Question

Does it make sense to run abyss on the said architectures at all? While it is probably interesting to know that there is a potential issue it would probably be a solution to declare the program 64 bit only and we (the Debian Med team who is maintaining the package) can restrict the list of architectures to exclude 32 bit architectures.

Kind regards, Andreas.

[jwcodee]

Hi Andreas, as of this moment we are still supporting the 32-bit arch. Our CI include 32-bit compilation tests and the builds do pass them. We will try to fix the error that you see as soon as possible.

[tillea]

Am Wed, Dec 08, 2021 at 03:38:34PM -0800 schrieb Johnathan Wong:

Hi Andreas, as of this moment we are still supporting the 32-bit arch. Our CI include 32-bit compilation tests and the builds do pass them. We will try to fix the error that you see as soon as possible.

Thanks a lot for your support, Andreas.

[vlad0x00]

I am not sure it makes sense for us to keep supporting 32 bit. I would never recommend anybody to run ABySS on a 32 bit machine and we can't guarantee that it would run as expected as we don't test whether things work well on such platforms (other than that ABySS compiles). @jowong4 Do you think it makes sense for us to keep supporting it?

[tillea]

Am Mon, Dec 20, 2021 at 10:52:26AM -0800 schrieb Vladimir Nikolić:

I am not sure it makes sense for us to keep supporting 32 bit. I would never recommend anybody to run ABySS on a 32 bit machine and we can't guarantee that it would run as expected as we don't test whether things work well on such platforms (other than that ABySS compiles).

I think its a perfectly valid solution of the problem to exclude the affected architectures. I just wanted to make sure you developers would confirm this. Kind regards, Andreas.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your interest in ABySS!

[tillea]

Am Mon, Jan 10, 2022 at 05:52:42PM -0800 schrieb github-actions[bot]:

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your interest in ABySS!

I think it can be closed *if* and only if you declare that ABySS is not supporting 32bit (any more).

[jwcodee]

Hi Andreas, we've discussed as team and decided we will no longer support 32-bit ABySS going forward. While we do try to ensure the binaries compile, we cannot test the quality of assemblies they generate so it doesn't make sense for us to support them. If users want to download 32-bit ABySS, they can do so by downloading older versions of ABySS.