Originally posted by Weasel
View Post
Originally posted by Weasel
View Post
Originally posted by Weasel
View Post
Originally posted by Weasel
View Post
Really this with C and C++ is so wrong its not funny that you have to store global symbols. If C/C++ has to work always by global symbols how can you use it with PE format.
C and C++ compilers are allowed to add extra information as the standard don't forbid extending. The two foo in that lwn.net are appear in the ELF static link table with extra information on linking handling. Just because format stores extra information like the STT_FILE in static linking so you can back trace what object a function comes from does not mean the linker cannot do a global resolve. So no object formats don't have to be able to store global symbols for C or C++ to work. The linker has to be able to process global symbols to fill in the blanks for C standard to work. Same way coff to PE link process fills in the blanks but this can in fact been done at the object static link and is with different ELF linkers.
Originally posted by Weasel
View Post
Like it or not PE/COFF if you go to the base specifications has the problem and always has had.
Weasel how much did you get right in your recap basically nothing.
Comment