summaryrefslogtreecommitdiffhomepage
path: root/proto-ft
diff options
context:
space:
mode:
authorStanislaw Halik <sthalik@misaki.pl>2018-02-01 09:34:48 +0100
committerStanislaw Halik <sthalik@misaki.pl>2018-02-01 09:34:48 +0100
commit18e775251a583a2b9000bcf3297d99fdc5035ead (patch)
tree8d45462975835f3507bf8827e693a43b225159d3 /proto-ft
parent71f5aac8d639a2fd6f18ae313a9d8784711049f1 (diff)
proto/ft: remove incorrect check
The data is aligned because it's inside a union with minimal alignment for `int'. The comment and check are redundant.
Diffstat (limited to 'proto-ft')
-rw-r--r--proto-ft/ftnoir_protocol_ft.cpp4
1 files changed, 0 insertions, 4 deletions
diff --git a/proto-ft/ftnoir_protocol_ft.cpp b/proto-ft/ftnoir_protocol_ft.cpp
index 654cd3b1..ae8fe5a2 100644
--- a/proto-ft/ftnoir_protocol_ft.cpp
+++ b/proto-ft/ftnoir_protocol_ft.cpp
@@ -118,10 +118,6 @@ void freetrack::pose(const double* headpose)
if ((std::intptr_t(pMemData) & page_size() - 1) != 0)
assert(!"proto/freetrack: memory mapping not page aligned");
- // the data happens to be aligned by virtue of element ordering
- // inside `FTHeap'. there's no deeper reason behind it.
- static_assert((offsetof(FTHeap, table) & sizeof(int) - 1) == 0, "");
-
// no atomic access for `char'
for (unsigned k = 0; k < 2; k++)
store(pMemData->table_ints[k], t.ints[k]);