.text - one of the few sections in the file you're unlikely to find *any* readable ASCII text in COMDAT - "common data" sections. primarily used to store code (that is defined in multiple translation units), not data.
-
-
এই থ্রেডটি দেখান
-
shared object - also not that kind of object, but not the other kind either. Generally stored in a file, which is however not an object file.
এই থ্রেডটি দেখান -
ELF - Executable and Linkable Format. Used primarily for object files, which are not executable but linkable, binaries, which are executable but not linkable, and core dumps, which are neither.
এই থ্রেডটি দেখান -
And on the subject of "binaries", this term is commonly used to refer to files containing machine code and data in a format the OS knows how to handle directly, because such files are generally stored in memory and on disk in a binary format. Just like all other files.
এই থ্রেডটি দেখান
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
thunk, veneer, etc
-
text segment is my personal favorite, and also every time I teach OS I tell students to just look up what BSS stands for, if they care
-
wait what's veneer?
-
it's like a thunk, which is like a trampoline
-
(veneer is the usual ARM term for trampolines that are inserted by the linker for what would otherwise be out-of-range branch targets)
-
I never heard it before, or else wasn't paying attention
-
it is one of those things where you think "having a separate special name for that probably causes more confusion than it is worth in added specificity", or at least I do
-
in linkerland you just say words and they mean whatever you want
- 3টি আরও উত্তর
নতুন কথা-বার্তা -
-
-
Linkers are like a history of proprietary undocumented tech accidentally exposed to the general public.
-
my favorite thing there is the history of COMDAT sections for code generated from templates
-
COMDAT sections originally existed in object formats as a fairly direct mapping of FORTRAN 77 named COMMON blocks (https://www.obliquity.com/computer/fortran/common.html …) which are a funky feature with no C equivalent that lies somewhere in the space between unions, structs and global variables
-
then someone somewhere (I think it was either at Borland or MS) realized you could (ab)use the same mechanism on code sections to get "just keep a single copy" semantics, and suddenly this formerly obscure sideshow was a core feature for C++ linking
-
load-bearing duct tape
-
what a perfect description of 80s/90s PC ecosystem system-level hacks :-)
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
-
-
ooh, do "weak" next!
-
honestly that's so overloaded I wouldn't know where to start
কথা-বার্তা শেষ
নতুন কথা-বার্তা -
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।