search for: __sym_attr_metadata

...mation into the compiled object file that tells the downstream linker about these memory placement constraints on the data objects and function. Without extending the ELF object format, how would this work? I propose to encode metadata information about a symbol in special absolute symbols, "__sym_attr_metadata.<int>", that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: typedef struct { Elf32_Word st_name; Elf32_Addr st_value; Elf32_Word st_size; unsigned char st_info; unsigned c...

...ile that tells the downstream linker about these memory placement constraints on the data objects and function. > > > > Without extending the ELF object format, how would this work? > > > > I propose to encode metadata information about a symbol in special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: > > > > typedef struct { > > Elf32_Word st_name; > > Elf32_Addr st_value; > > Elf32_Word st_size; >...

...nker about these memory placement constraints on the data objects and function. > > > > Without extending the ELF object format, how would this work? > > > > I propose to encode metadata information about a symbol in special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: > > > > typedef struct { > > Elf32_Word st_name; > > Elf32_Addr st_value; >...

...> > > > > > > > > > > > Without extending the ELF object format, how would this work? > > > > > > > > > > > > I propose to encode metadata information about a symbol in special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: > > > > > > > > > > > > typedef struct { > > > > > > Elf32_Word st_name; &gt...

...> > > > > > > > > > > > Without extending the ELF object format, how would this work? > > > > > > > > > > > > I propose to encode metadata information about a symbol in special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can recognize when scanning the symbol table for an incoming object file. In an ELF symbol table entry: > > > > > > > > > > > > typedef struct { > > > > > > Elf32_Word st_name; &gt...

...t; >> > > > Without extending the ELF object format, how would this work? >> > > > >> > > > >> > > > >> > > > I propose to encode metadata information about a symbol in >> special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can >> recognize when scanning the symbol table for an incoming object file. In an >> ELF symbol table entry: >> > > > >> > > > >> > > > >> > > > typedef struct { >> > >...

...t; > > > > > > > > Without extending the ELF object format, how would this work? > > > > > > > > > > > > > > > > I propose to encode metadata information about a symbol in > special absolute symbols, “__sym_attr_metadata.<int>”, that the linker can > recognize when scanning the symbol table for an incoming object file. In an > ELF symbol table entry: > > > > > > > > > > > > > > > > typedef struct { > > > > > > >...