Re: The different groups and segments of object files

Am 19.06.2020 um 17:22 schrieb Johann 'Myrkraverk' Oskarsson:


> When I am defining my own compiler, do the traditional names of object
> file segments, _TEXT, _DATA, STACK, _BSS, CONST (to name a few from the
> MS manual) any meaning?  When I place my code in a _TEXT segment, the
> disassembler will show a list of the instructions; this does not happen
> if I name the segment FOO.  Is there any particular reason I want my
> code in a _TEXT segment rather than FOO?


I think that it's not the segment name that enforces special handling
but segment attributes. Eventually these attributes are defined in the
various segment groups only, not at segment level?


It depends on the target OS and hardware whether deailed hardware
protection is applied to memory segments. Code segments can be read-only
or execute-only, all others non-execute. Const segments also can/should
be read-only. The same protection schemes can apply to paged memory. A
compiler only can assign attributes to memory sections, the use of these
attributes depends on the linker and loader for the target platform.


DoDi

Return to the comp.compilers page.
Search the comp.compilers archives again.