On 15.08.2026 03:20, Richard Wheeler wrote:
Each access gets its own descriptor (no memoization)
Well, I mean, what can we say that you don't already know? If the question is whether in tinycc we want to confine us with some intermediate take with still obvious drawbacks such as redundant duplicate entries, then the answer is no, of course. If the questions is whether in tinycc we do like ugly hacks such as
+static void tlv_patch_descriptor_offsets(struct macho *mo)
then the answer is actually no, also. Nobody likes ugly hacks. At least not if one could just use a proper TLS relative relocation type instead. Or even invent one if nothing else. If it were me, I would maybe try to build the entire descriptor table later in the link step, with one entry for each STT_TLS type symbol. Basically what you already have, just operating on ELF symbols and in a 'for (...)' loop. Also there is 144_tls.test which you might want to enable (un-skip) for OSX/ARM64 once you have everything in place and working seamlessly as it should. -- gr _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
