From 8f8bf24e4c90ffb35010cbed27f4a54859c8e1cf Mon Sep 17 00:00:00 2001 From: Mathias Kraus Date: Fri, 27 Sep 2024 11:32:40 +0200 Subject: [PATCH] iox-#2301 Better wording --- doc/website/advanced/iceoray-on-32-bit.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/website/advanced/iceoray-on-32-bit.md b/doc/website/advanced/iceoray-on-32-bit.md index 463b6096a1..e86f89a8ff 100644 --- a/doc/website/advanced/iceoray-on-32-bit.md +++ b/doc/website/advanced/iceoray-on-32-bit.md @@ -56,9 +56,9 @@ struct Foo { }; ``` -As long as the bitness it the same, one does not have to care. -But when 32-bit and 64-bit applications are connected via shared memory, both applications have to agree to a common layout, otherwise the applications will misbehave. -In the worst case, the application keeps running with invalid data and in the best case it leads to an immediate segmentation fault. +As long as the applications share the same bitness, there is no need for special consideration. +However, when connecting 32-bit and 64-bit applications via shared memory, both must adhere to a common memory layout. +If the layout differs, it can lead to unpredictable behavior and errors in the applications. The simplest way to fix this specific alignment issue, is to use the `-malign-double` flag, which enforces an 8 byte alignment boundary for 64-bit data types on 32-bit architectures.