[Octave-bug-tracker] [bug #59149] [octave forge] (signal) Resampling from 22050 to 48000 Hz introduces strange and unexpected artifacts

[anonymous]

Follow-up Comment #21, bug #59149 (project octave):

I did a long series of experiments for some hours. The clincher is not the
march=native, but using -Ofast to build the packages. The base Octave
installation can be compiled with O0, O2 or O3, with or without march=native
-- it doesn't make much difference. But before running "pkg install -forge",
set  the environment variables CFLAGS, CXXFLAGS and FFLAGS to include -Ofast.
I verify that it works without march=native, at least with GCC 10.2.0.

As always, -Ofast will likely break strict standards-compliance. The fact that
it gives the correct answer when plain -O2 and -O3 cause problems in this case
might point to a numerical bug hidden somewhere that is being "optimized away"
with -Ofast but is present with safer optimizations.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59149>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/