|
From: | Rafael Laboissiere |
Subject: | [Octave-bug-tracker] [bug #59830] Architecture-dependent results for arithmetic operations involving NA |
Date: | Tue, 19 Jan 2021 03:54:22 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 |
Follow-up Comment #15, bug #59830 (project octave): [comment #13 comment #13:] > If so, this isn't that hard a fix. There will need to be a configure test written to determine whether Octave is compiling on a MIPS architecture and then there will need to be an #ifdef in lo-ieee.h to choose between two different definitions of LO_IEEE_NA_HW. We should also ensure the interoperability between the different architectures. For instance, if we run the following code on a amd64 system: octave:1> x = NA; octave:2> save -binary x.dat x I get now the following on mips64el with the patched Octave, when trying to load the file saved on amd64: octave:1> load x.dat octave:2> x x = NaN _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59830> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |