3 ms·
Fortunately, almost nobody really cares.
by kstenerud 6y ago
Fortunately, almost nobody really cares.
- pjmlp 6y agoI bet those that will never get some critical performance optimizations on their clang compiler, or are hoping for a BSD desktop revolution will care.
- kstenerud 6y agoIf nomenclature is the reason for withholding features and development, you've got other problems.
- pjmlp 6y agoNomenclature sometimes means a complete different license model.
- saagarjha 6y agoI mean, macOS is a thing and it’s just one of the many things built using Clang…
- pjmlp 6y agoPity that LLVM doesn't get those bitcode improvements used in watchOS and macOS clang is different enough to warrant its own column on cppreference. Lets see how much Apple Silicon specific optimizations will be upstreamed.
- saagarjha 6y agoApple’s strange ABI is upstreamed: https://github.com/llvm/llvm-project/search?q=arm64_32&unscoped_q=arm64_32 https://github.com/llvm/llvm-project/search?q=arm64_32&unsco.... Not sure what “column” you’re talking about, but it’s fairly clear that macOS’s clang is based on a fairly recent LLVM that they branched off of (you can even grab the underlying version number if you know where to look). And profiles for Apple silicon chips are readily available: https://github.com/llvm/llvm-project/blob/954db63cd149df031d9b660bf68f0fe1de1defb9/llvm/include/llvm/Support/AArch64TargetParser.def#L145 https://github.com/llvm/llvm-project/blob/954db63cd149df031d.... LLVM is probably one of the projects from Apple that sees the most things get upstreamed.
- pjmlp 6y agoMentioned bitcode, not ABI. Easy to find out which column I mean, https://en.cppreference.com/w/cpp/compiler_support https://en.cppreference.com/w/cpp/compiler_support I did not say that they wouldn't upstream Apple Silicon support, rather that they won't upstream everything, just as most OEMs make with their LLVM forks.