aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-01-29 17:38:15 -0500
committerNick Mathewson <nickm@torproject.org>2013-01-29 17:38:15 -0500
commit73d605b0f759a2ff9f859f78f76098dcdb290d37 (patch)
tree6293cd558c73359e726a40c8d6157af08be7cd35 /changes
parenta0351311aeea715cea24e156e065b65cc29a804c (diff)
downloadtor-73d605b0f759a2ff9f859f78f76098dcdb290d37.tar
tor-73d605b0f759a2ff9f859f78f76098dcdb290d37.tar.gz
Detect platforms where memset(0) doesn't set doubles to 0.0.
This is allowed by the C statndard, which permits you to represent doubles any way you like, but in practice we have some code that assumes that memset() clears doubles in structs. Noticed as part of 7802 review; see 8081 for more info.
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 000000000..74554cd27
--- /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.
+