Re: octave: update to 7.3.0.

[tornaria <tornaria@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

New comment by tornaria on void-packages repository

https://github.com/void-linux/void-packages/pull/40720#issuecomment-1340076459

Comment:
The testsuite was giving a segfault on i686, when using `qr` on a sparse matrix. In fact this is trivial to reproduce:
```
octave:1> qr(sparse(1,1));
fatal: caught signal Segmentation fault -- stopping myself...
Segmentation fault
```
I "solved" it by using `--without-spqr` on i686 builds.

---

Then there are a couple of test failures seemingly due to numerical unstability, but they are not fixed with the standard tricks (`-ffloat-store`, `-mfpmath=sse`, etc). At least one is unrelated to octave as I can reproduce with:
```
$ cat sin.cc 
#include <complex>
#include <iostream>

int main()
{
	std::complex<double> c(-1.3962634015954636, 3.141592653589793);
	std::complex<double> d(-11.415845458288851, 2.0054175437381652);
	std::complex<double> e = std::sin(c) - d;

	std::cout << e << std::endl;
}
$ g++ sin.cc -o sin && ./sin                    
(-1.77636e-15,0)
```
The same code on x86_64 gives `(0,0)`.