Changes between Version 3 and Version 4 of Ticket #406
- Timestamp:
- 09/01/2026 08:58:33 AM (4 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #406 – Description
v3 v4 35 35 2 call_data_ptr ptr, /* For event call channels -- something to tell them. */ 36 36 2 call_priority fixed bin (17), /* For event call channels -- who's first? */ 37 2 pad5 fixed bin, 37 38 38 39 ipc_create_arg_structure_ptr ptr; … … 53 54 2 pad2 variable entry (ptr), 54 55 2 pad3 ptr, 55 2 pad4 fixed bin; 56 2 pad4 fixed bin, 57 2 pad5 fixed bin; 56 58 57 59 … … 65 67 /* -- output ptr which locates fast_event_bit */ 66 68 2 pad4 fixed bin, 69 2 pad5 fixed bin, 67 70 68 71 fast_event_bit bit(1) unaligned based (ipc_create_fast_event.event_bit_ptr); … … 84 87 }}} 85 88 86 The pad1 element is missing, but the gap between channel_type and call_entry still exists, because the entry data type must be aligned on an even-word boundary. Coding standards require that all space within a public structure be explicitly declared. So I have added the pad1 element to represent this hidden space in my proposal above.89 The pad1 and pad5 elements are missing, but the gap between channel_type and call_entry still exists, because the entry data type must be aligned on an even-word boundary; and the pad5 word does exist because the entire structure is aligned on a double-word boundary and is an even number of words in length. Coding standards require that all space within a public structure be explicitly declared. So I have added the pad1 element to represent this hidden space in my proposal above.
