aboutsummaryrefslogtreecommitdiffstats
path: root/xcomp/README.md
diff options
context:
space:
mode:
authorMike Sperber <[email protected]>2012-03-22 18:00:31 +0100
committerMike Sperber <[email protected]>2012-03-23 09:15:19 +0100
commit933e701dac1936c6f15c765b5687fbc623464ec7 (patch)
tree95bef4a51a14f512c23348e39cbfb336bc22475b /xcomp/README.md
parent3087769515ea9bfc75f7d7b8897bc897c7f13931 (diff)
downloadotp-933e701dac1936c6f15c765b5687fbc623464ec7.tar.gz
otp-933e701dac1936c6f15c765b5687fbc623464ec7.tar.bz2
otp-933e701dac1936c6f15c765b5687fbc623464ec7.zip
Unbreak floating point on middle-endian machines.
On some ARMs (and maybe other platforms), doubles are stored with the the two 32-bit words reversed with respect to more common architectures. The symptom is this: > io_lib:write(1.0). "0.000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005299808824" Detect that and account for it when decoding floats.
Diffstat (limited to 'xcomp/README.md')
-rw-r--r--xcomp/README.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/xcomp/README.md b/xcomp/README.md
index 2d79107283..98e71d5962 100644
--- a/xcomp/README.md
+++ b/xcomp/README.md
@@ -430,6 +430,14 @@ When a variable has been set, no warning will be issued.
`configure` will fail unless this variable is set. Since no default
value is used, `configure` will try to figure this out automatically.
+* `erl_xcomp_double_middle` - `yes|no`. No default. If `yes`, the
+ target system must have doubles in "middle-endian" format. If
+ `no`, it has "regular" endianness. This can often be automatically
+ detected, but not always. If not automatically detected,
+ `configure` will fail unless this variable is set. Since no
+ default value is used, `configure` will try to figure this out
+ automatically.
+
* `erl_xcomp_clock_gettime_cpu_time` - `yes|no`. Defaults to `no`. If `yes`,
the target system must have a working `clock_gettime()` implementation
that can be used for retrieving process CPU time.