bebbo
commented
1 year ago now you have to provide these by yourself and put that into the correct sections.
.section .list___INIT_LIST__,"aw"
___INIT_LIST__:
.long 0
.section .list___EXIT_LIST__,"aw"
___EXIT_LIST__:
.long 0which can also be done in C with
__attribute__((section(".list___INIT_LIST__")))
long __INIT_LIST__[] = {0};
__attribute__((section(".list___EXIT_LIST__")))
long __EXIT_LIST__[] = {0};That object file must be the first one. The linker collects the other entries into the same section. The value here is just a dummy and replaces the previously existing count.
Plus you need an exit object to append the a final 0.
__attribute__((section(".list___INIT_LIST__")))
long __INIT_LIST_END[] = {0};
__attribute__((section(".list___EXIT_LIST__")))
long __EXIT_LIST_END[] = {0};Since elf doesn't support constructors and constructors are causing pita using sections per function,.. I've chosen this way.
You could achieve the same with an appropriate linker script, but that again causes hickups, e.g. kills the feature to insert jump tables if -smallcode is used.
mheyer32
DoomAttack fails to link with a recent version of the toolchain with:
The plugins in DoomAttack are a curious thing... I had to remind myself how that works. They get loaded at runtime via LoadSeq and compiled via
-nostartfiles -lstubs. The plugins may use libnix functionality like printf; thus need some form of libnix initialization.Back then I worked around the issue by providing my own InitRuntime() and CleanupRuntime() functions that emulate what the toolchain's runtime initialization for libs etc.:
https://github.com/mheyer32/DoomAttack/blob/master/gnudoom/plugin_runtime.c
There I refer to
That doesn't seem to work anymore. Do you have some advice on how to do this better and get it working again?