5 ms·

Now if only Apple would quit mysteriously stripping out features from the full LLVM release...

• bluejekyll 9y ago
  What are they stripping out?
  • gcp 9y ago
    OpenMP, for one. They at least used to strip thread_local too.
    • rleigh 9y ago
      Working in scientific software development, I've seen quite a few people developing on Macs who would really appreciate OpenMP support. They end up having to use GCC or a vanilla Clang, but it's extra work and it comes with its own caveats.
      • nerdponx 9y ago
        Or just `brew install llvm` and `CC=/usr/local/opt/llvm/bin/clang`.
        • saghm 9y ago
          Naive question: Isn't this just "vanilla clang" that GP refers to?
          • rleigh 9y ago
            Yes.
          • nerdponx 9y ago
            I misunderstood, thanks.
    • DannyBee 9y ago
      They just don't ship the runtime library, no?
• Karliss 9y ago
  It seems more likely that they simply don't use upstream release tags and put their changes and maybe backport some changes on top of randomly chosen revision. The same way as Google released Android ndk r15 few months ago with clang "5.0". The sad part is that their version is neither older or newer than official release as it doesn't contain everything from upstream release and upstream doesn't contain all of their changes yet.
  • 0x0 9y ago
    It can't possibly be pure coincidence that a major llvm release is timed about one week off from the annual major apple macOS/iOS/toolchain + iPhone hardware release, with their history of employing big llvm contributors?
    • theresistor 9y ago
      It is. The tool chain going into those releases is locked down months in advance.