LLVM IR isn't platform-independent ʟʟᴠᴍ ɪʀ ɪsɴ'ᴛ ᴘʟᴀᴛғᴏʀᴍ-ɪɴᴅᴇᴘᴇɴᴅᴇɴᴛ ʇuǝpuǝdǝpuᴉ ɯɹoɟʇɐld ʇ,usᴉ ɹI WΛ˥˥ Ļ̥̰͉̲L̺V̥̲̖̥̣̝͝M͓̖͇ I͍͓R͇͓̝͍ ̵̪͇͖̻ị͔̺̫͚͟s̞͙̯͓͍̭̗n̝'͚t̟͇͖͉̖̖̀ͅ p̴͇̣ĺ̞a̗̤͓̟͚̤̭͜t̗̺̻̬f̵̰̗̬̙ơ̗͔̭̞̱rm̶͙͙͓̲̖͉-ḭ̲̭̣n̕deͅp͖̣͜e̡̜̮̗̤n҉̟̥̭d̴̳̮͍͎̝̫e̩̣͉͔͇̝͝ͅn̟͓ͅt̺̞̼͍̀
-
-
Replying to @FioraAeterna @whitequark
This is really a corollary of C and C++ not being platform-independent (i.e. having ways to observe properties like endianness from inside the language due to RoT).
1 reply 0 retweets 1 like -
Replying to @RichFelker @whitequark
LLVM IR has some extra non-independent bits as well (ABI, data layout, intrinsics)
2 replies 0 retweets 3 likes -
but yeah, the ifdefs and language-specific stuff from C is basically fatal at the start.
1 reply 0 retweets 2 likes -
Replying to @FioraAeterna @whitequark
You could opt to choose canonical type sizes, endianness, etc. and use that on all platforms, of course, but it would have nontrivial cost & wouldn't match existing platform ABIs.
2 replies 0 retweets 0 likes -
Isn't that just called PNaCl?
1 reply 0 retweets 2 likes
Yeah pretty much.
11:51 AM - 12 Jan 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.