search for: fsymbol

...be loaded if the feature partition is also loaded. (Which is the same reason why direct pc-relative references from the feature partition to the main partition will also work.) I don't think any significant IR extensions are necessary here, except perhaps for the part involving attaching the -fsymbol-partition names to globals, but I think that part is mostly trivial and it would probably end up looking like the custom section name field. I'm not sure I understand how weak linkage is impacted here. With this nothing special happens inside the linker until we start handling --gc-sections, a...

...file. These slices can also be fed to tools such as debuggers provided that the non-SHF_ALLOC sections are left in place. The envisaged usage of this feature is as follows: $ clang -ffunction-sections -fdata-sections -c main.c # compile the main program $ clang -ffunction-sections -fdata-sections -fsymbol-partition=libfeature.so -c feature.c # compile the feature $ clang main.o feature.o -fuse-ld=lld -shared -o libcombined.so -Wl,-soname,libmain.so -Wl,--gc-sections $ llvm-objcopy libcombined.so libmain.so --extract-partition=libmain.so $ llvm-objcopy libcombined.so libfeature.so --extract-partition...

...provided that the non-SHF_ALLOC >> sections are left in place. >> >> The envisaged usage of this feature is as follows: >> $ clang -ffunction-sections -fdata-sections -c main.c # compile the main >> program >> $ clang -ffunction-sections -fdata-sections >> -fsymbol-partition=libfeature.so -c feature.c # compile the feature >> $ clang main.o feature.o -fuse-ld=lld -shared -o libcombined.so >> -Wl,-soname,libmain.so -Wl,--gc-sections >> $ llvm-objcopy libcombined.so libmain.so --extract-partition=libmain.so >> $ llvm-objcopy libcombined....