History

modules: Add missing entry for __ex_table

The entry for __ex_table was missing, which may make __ex_table become 1- or 2-byte aligned in modules. Add the entry to ensure it gets 32-bit aligned. As per unaligned-memory-access [0] "unaligned memory accesses [...] will not work correctly on certain platforms and will cause performance problems on others", so fix this.

Helge Deller committed 2 years ago

Commit 03ddd2f1 parent 335de241 file · +1 −0Browse files

Showing the changes to scripts (1 of 1 file). Show all

Unified · Split

scripts/module.lds.S+1−0
@@ -29,6 +29,7 @@ SECTIONS { · 28 unmodified lines
29 .altinstructions 0 : ALIGN(8) { KEEP(*(.altinstructions)) }29 .altinstructions 0 : ALIGN(8) { KEEP(*(.altinstructions)) }
30 __bug_table 0 : ALIGN(8) { KEEP(*(__bug_table)) }30 __bug_table 0 : ALIGN(8) { KEEP(*(__bug_table)) }
31 __jump_table 0 : ALIGN(8) { KEEP(*(__jump_table)) }31 __jump_table 0 : ALIGN(8) { KEEP(*(__jump_table)) }
32 __ex_table 0 : ALIGN(4) { KEEP(*(__ex_table)) }
32 33
33 __patchable_function_entries : { *(__patchable_function_entries) }34 __patchable_function_entries : { *(__patchable_function_entries) }
34 35