summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-01-31 13:19:27 -0500
committerNick Mathewson <nickm@torproject.org>2013-01-31 13:19:27 -0500
commitb35b4d5a9a9967da9416fc8d2112910f00529967 (patch)
tree73e13824a69a95cc832bb9f16603830b9f4eaa65 /changes
parentb0dd35589124ba596532b3640d28dfb21989b590 (diff)
parent73d605b0f759a2ff9f859f78f76098dcdb290d37 (diff)
downloadtor-b35b4d5a9a9967da9416fc8d2112910f00529967.tar.gz
tor-b35b4d5a9a9967da9416fc8d2112910f00529967.zip
Merge branch 'double-0-check'
Diffstat (limited to 'changes')
-rw-r--r--changes/double-0-check8
1 files changed, 8 insertions, 0 deletions
diff --git a/changes/double-0-check b/changes/double-0-check
new file mode 100644
index 0000000000..74554cd272
--- /dev/null
+++ b/changes/double-0-check
@@ -0,0 +1,8 @@
+ o Build improvements (bizarre platform detection):
+ - Try to detect it if we are ever building on a platform where
+ memset(...,0,...) does not set the value of a double to 0.0. Such
+ platforms are permitted by the C standard, though in practice
+ they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
+ currently support them, but it's better to detect them and fail
+ than to perform erroneously.
+