Talk:Memory layout of a data structure: Difference between revisions
Content added Content deleted
(Created page with "Most of the "solutions" here fail because they don't actually control the memory layout. Most of these data structures have no way to be mapped to an arbitrary address such as a ...") |
(Re-read.) |
||
| Line 1: | Line 1: | ||
Most of the "solutions" here fail because they don't actually control the memory layout. Most of these data structures have no way to be mapped to an arbitrary address such as a hardware register, such that the fields line up with the bits there, and can be used for individual access. |
Most of the "solutions" here fail because they don't actually control the memory layout. Most of these data structures have no way to be mapped to an arbitrary address such as a hardware register, such that the fields line up with the bits there, and can be used for individual access. |
||
:Read the task description again and if you adhere to what it says you will note that mapping a data structure to an arbitrary address is ''not'' part of the task. --[[User:Paddy3118|Paddy3118]] 18:06, 20 September 2011 (UTC) |
|||
Revision as of 18:06, 20 September 2011
Most of the "solutions" here fail because they don't actually control the memory layout. Most of these data structures have no way to be mapped to an arbitrary address such as a hardware register, such that the fields line up with the bits there, and can be used for individual access.
- Read the task description again and if you adhere to what it says you will note that mapping a data structure to an arbitrary address is not part of the task. --Paddy3118 18:06, 20 September 2011 (UTC)