[Bug 3318] Inconsistency between .rdata and .rodata sections


bugzilla-daemon@...
 

https://bugzilla.tianocore.org/show_bug.cgi?id=3318

--- Comment #5 from Marvin Häuser <mhaeuser@posteo.de> ---
Actually, I forgot that we can use preprocessor definitions in NASM. This makes
this a far simpler matter of:
"SECTION RO_DATA_SECTION_NAME" in NASM
"RELEASE_VS2019_X64_NASM_FLAGS = -Ox -f win64 -DRO_DATA_SECTION_NAME=.rdata";
"*_XCODE5_X64_NASM_FLAGS = -f macho64 -DRO_DATA_SECTION_NAME=.rodata";
"*_CLANGPDB_X64_NASM_FLAGS = -f win64
-DRO_DATA_SECTION_NAME=.rodata"; [...]
in tools_def.template

However, I also noticed that ELF-based toolchains (GCC5, CLANG38) merge
".rodata" into ".text", PE toolchains (VS2019, CLANGPDB) however generate a
separate ".rdata" section. Should this be made consistent?

--
You are receiving this mail because:
You are on the CC list for the bug.

Join bugs@edk2.groups.io to automatically receive all group messages.