12 ms·

LLVM 8.0.0 Release

302 points by samber 8y ago

0x0 8y ago
Are LLVM releases always timed to align with Xcode releases these days? I guess most people expect new Xcode and iOS/Mac SDKs on Monday.
- AlexeyBrin 8y ago
  Not really, Clang and LLVM from Apple (the version that comes with Xcode) is usually behind the official LLVM release and it is also slightly modified/patched.
- pavlov 8y ago
  Really? What's happening on Monday? Seems like unusual timing for SDK updates, a few months early of the usual WWDC releases...
  - rudedogg 8y ago
    It'll just be a point/minor release. WWDC is where major releases are usually announced (iOS 13 and macOS 10.15 for the coming 2019 WWDC).
- wyldfire 8y ago
  I think it's ~6 month cycles so it might end up lining up with an annual event for a while. But soon enough they'll probably be out of phase.
- coldtea 8y ago
  >I guess most people expect new Xcode and iOS/Mac SDKs on Monday. Most people don't expect them then, and they'd be wrong if they do. Apple just has one of the regular spring-time announcements for hardware and services products. WWDC, when the new Xcode and iOS/Mac SDKs will be announced (but usually not released to non-devs until Fall), is, and has always been, in the summer (June). (And there's another hardware/services announcement in Fall usually).
  - 0x0 8y ago
    It's expected that iOS 12.2 is coming with Swift5, and ABI stability for the first time, as well as os-bundled libswift for the first time. Sounds like a semi major sdk update to me.
    - coldtea 8y ago
      Hmm, the minor update with new Swing is indeed a good point. Not the usual way it happens though. Usually those things came at WWDC.
- Someone 8y ago
  It wouldn’t surprise me if Monday were television series, only. Alternatively, it’s that plus “one more thing”, where that thing is big. I’m thinking that because the 70% faster iPad and the 100% faster iMac apparently didn't make the cut for Monday.
zmodem 8y ago
https://news.ycombinator.com/item?id=19441297 https://news.ycombinator.com/item?id=19441297 links to the release announcement for the whole project, not just the LLVM module.
- aboutruby 8y ago
  The other post has no comments yet and the link is: https://lists.llvm.org/pipermail/llvm-announce/2019-March/000082.html https://lists.llvm.org/pipermail/llvm-announce/2019-March/00...
  - sctb 8y ago
    OK, we'll update this link from http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html.
- AndrewGaspar 8y ago
  This link is definitely more interesting if you care about clang or clang tools.
zegl 8y ago
I've been wanting to test out the LLVM IR to WebAssembly compilation, but I've been too lazy (or impatient) to compile LLVM from source. Nice to see that it's now enabled by default!
- slacka 8y ago
  There truly is nothing to it. I just built it for the first time on this fresh install of Ubuntu. You can just copy and paste the lines from the getting started page.[1] Here's my .bash_history: $ git clone https://github.com/llvm/llvm-project.git $ cd llvm-project $ mkdir build && cd build $ cmake -DLLVM_ENABLE_PROJECTS=clang -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" ../llvm $ make -j4 Took < 40 min on an old laptop. [1] https://clang.llvm.org/get_started.html https://clang.llvm.org/get_started.html
  - atq2119 8y ago
    It doesn't matter much when you build only once, but more people need to be aware of Ninja for builds. Both cmake and meson can target it, and it is much faster for incremental builds.
    - RantyDave 8y ago
      I never understand this. Surely 'make' itself uses an almost irrelevantly low amount of CPU compared to compiling? That being said: have used Ninja with Cmake. Damn fast.
      - maccam912 8y ago
        It's not so much how much CPU each takes up, but that 'make' will waste some time recompiling stuff that doesn't need to be recompiled. Ninja is better about reusing stuff compiled the first time to make the second compilation faster but still accurate.
        coherentpony 8y ago
wyldfire 8y ago
> -mspeculative-load-hardening Clang now has an option to enable Speculative Load Hardening. I wonder -- which targets support this flag? And which ones need it (i.e. which are susceptible)? Also, I didn't see it in the changelog -- does libc++ have std::execution::* yet?
aquabeagle 8y ago
edit: nevermind
- zmodem 8y ago
  The link makes it sound like the switch happens after the 8.0.0 release.
- aepiepaey 8y ago
  No, it does not. According to you reference link: > We currently plan to install the new developer policy and add the new license in January 2019 after the LLVM 8.0 release has branched. Also, the source archive for LLVM 8 still contains the old license. Which means that the first release under the Apache 2 license should be LLVM 9.
openbasic 8y ago
Wish they updated the Kaleidoscope tutorial.
benchaney 8y ago
Does anyone know what the status of the llvm riscv backend is? I haven’t heard about it in a while.
- smitty1110 8y ago
  LLD just added support for that architecture with this release, so I assume it's still being actively developed.
- steveklabnik 8y ago
  rustc has support in-tree for riscv32imac-unknown-none-elf riscv32imc-unknown-none-elf riscv64gc-unknown-none-elf riscv64imac-unknown-none-elf So, it's at least far enough along to have that turned on!
  - bionicbits 8y ago
    Nice, was just looking into this!
    - steveklabnik 8y ago
      You have to $ rustup target add <triple> to download the pre-compiled libraries, but then it should be a --target <triple> away! As far as I know anyway, I'm sure there are bugs since it's so new.
newnewpdro 8y ago
I was able to get AMDGPU & Mesa-OpenCL working reliably on an AMD RX480 with this release. On 6 and 7 some OpenCL kernels would consistently fail with illegal instruction problems. If you've been using AMDGPU PRO just for OpenCL support, and prefer running mainline drivers, give AMDGPU a try on llvm8 and a recent kernel.
xvilka 8y ago
While they did an amazing job on improving the framework, compiler, and tools, a few important compatibility features weren't addressed: - '-MT' and '-MM' options support (like in GCC)[1] - '-M'/'-MF' options support (like in GCC)[2] - 'MENUEX' menu resource section parsing (like in MSVC)[3] Also, we recently found a problem[4] while compiling radare2 with 8.0.0 clang-cl for Windows. Hopefully, it will be addressed soon since the tool offers sanitizers support for the Windows platform, which is a blast. [1] https://bugs.llvm.org/show_bug.cgi?id=10091 https://bugs.llvm.org/show_bug.cgi?id=10091 [2] https://bugs.llvm.org/show_bug.cgi?id=8312 https://bugs.llvm.org/show_bug.cgi?id=8312 [3] https://bugs.llvm.org/show_bug.cgi?id=40108 https://bugs.llvm.org/show_bug.cgi?id=40108 [4] https://bugs.llvm.org/show_bug.cgi?id=41128 https://bugs.llvm.org/show_bug.cgi?id=41128
deleted 8y ago
[deleted]
xvilka 8y ago
I should also note that KLEE 2.0 was released[1] in line with LLVM 8.0 release. It is the first release in the last 2 years, so the amount of changes is huge. If you are using symbolic execution - I recommend you to check out this version. [1] https://github.com/klee/klee/releases/tag/v2.0 https://github.com/klee/klee/releases/tag/v2.0

302 points by samber 8y ago

0x0 8y ago

Are LLVM releases always timed to align with Xcode releases these days? I guess most people expect new Xcode and iOS/Mac SDKs on Monday.

AlexeyBrin 8y ago
Not really, Clang and LLVM from Apple (the version that comes with Xcode) is usually behind the official LLVM release and it is also slightly modified/patched.
pavlov 8y ago
Really? What's happening on Monday? Seems like unusual timing for SDK updates, a few months early of the usual WWDC releases...
- rudedogg 8y ago
  It'll just be a point/minor release. WWDC is where major releases are usually announced (iOS 13 and macOS 10.15 for the coming 2019 WWDC).
wyldfire 8y ago
I think it's ~6 month cycles so it might end up lining up with an annual event for a while. But soon enough they'll probably be out of phase.
coldtea 8y ago
>I guess most people expect new Xcode and iOS/Mac SDKs on Monday. Most people don't expect them then, and they'd be wrong if they do. Apple just has one of the regular spring-time announcements for hardware and services products. WWDC, when the new Xcode and iOS/Mac SDKs will be announced (but usually not released to non-devs until Fall), is, and has always been, in the summer (June). (And there's another hardware/services announcement in Fall usually).
- 0x0 8y ago
  It's expected that iOS 12.2 is coming with Swift5, and ABI stability for the first time, as well as os-bundled libswift for the first time. Sounds like a semi major sdk update to me.
  - coldtea 8y ago
    Hmm, the minor update with new Swing is indeed a good point. Not the usual way it happens though. Usually those things came at WWDC.
Someone 8y ago
It wouldn’t surprise me if Monday were television series, only. Alternatively, it’s that plus “one more thing”, where that thing is big. I’m thinking that because the 70% faster iPad and the 100% faster iMac apparently didn't make the cut for Monday.

zmodem 8y ago

https://news.ycombinator.com/item?id=19441297 https://news.ycombinator.com/item?id=19441297 links to the release announcement for the whole project, not just the LLVM module.

aboutruby 8y ago
The other post has no comments yet and the link is: https://lists.llvm.org/pipermail/llvm-announce/2019-March/000082.html https://lists.llvm.org/pipermail/llvm-announce/2019-March/00...
- sctb 8y ago
  OK, we'll update this link from http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html http://releases.llvm.org/8.0.0/docs/ReleaseNotes.html.
AndrewGaspar 8y ago
This link is definitely more interesting if you care about clang or clang tools.

zegl 8y ago

I've been wanting to test out the LLVM IR to WebAssembly compilation, but I've been too lazy (or impatient) to compile LLVM from source. Nice to see that it's now enabled by default!

slacka 8y ago
There truly is nothing to it. I just built it for the first time on this fresh install of Ubuntu. You can just copy and paste the lines from the getting started page.[1] Here's my .bash_history: $ git clone https://github.com/llvm/llvm-project.git $ cd llvm-project $ mkdir build && cd build $ cmake -DLLVM_ENABLE_PROJECTS=clang -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" ../llvm $ make -j4 Took < 40 min on an old laptop. [1] https://clang.llvm.org/get_started.html https://clang.llvm.org/get_started.html
- atq2119 8y ago
  It doesn't matter much when you build only once, but more people need to be aware of Ninja for builds. Both cmake and meson can target it, and it is much faster for incremental builds.
  - RantyDave 8y ago
    I never understand this. Surely 'make' itself uses an almost irrelevantly low amount of CPU compared to compiling? That being said: have used Ninja with Cmake. Damn fast.
    - maccam912 8y ago
      It's not so much how much CPU each takes up, but that 'make' will waste some time recompiling stuff that doesn't need to be recompiled. Ninja is better about reusing stuff compiled the first time to make the second compilation faster but still accurate.
      - coherentpony 8y ago

wyldfire 8y ago

> -mspeculative-load-hardening Clang now has an option to enable Speculative Load Hardening. I wonder -- which targets support this flag? And which ones need it (i.e. which are susceptible)? Also, I didn't see it in the changelog -- does libc++ have std::execution::* yet?

aquabeagle 8y ago

edit: nevermind

zmodem 8y ago
The link makes it sound like the switch happens after the 8.0.0 release.
aepiepaey 8y ago
No, it does not. According to you reference link: > We currently plan to install the new developer policy and add the new license in January 2019 after the LLVM 8.0 release has branched. Also, the source archive for LLVM 8 still contains the old license. Which means that the first release under the Apache 2 license should be LLVM 9.

openbasic 8y ago

Wish they updated the Kaleidoscope tutorial.

benchaney 8y ago

Does anyone know what the status of the llvm riscv backend is? I haven’t heard about it in a while.

smitty1110 8y ago
LLD just added support for that architecture with this release, so I assume it's still being actively developed.
steveklabnik 8y ago
rustc has support in-tree for riscv32imac-unknown-none-elf riscv32imc-unknown-none-elf riscv64gc-unknown-none-elf riscv64imac-unknown-none-elf So, it's at least far enough along to have that turned on!
- bionicbits 8y ago
  Nice, was just looking into this!
  - steveklabnik 8y ago
    You have to $ rustup target add <triple> to download the pre-compiled libraries, but then it should be a --target <triple> away! As far as I know anyway, I'm sure there are bugs since it's so new.

newnewpdro 8y ago

I was able to get AMDGPU & Mesa-OpenCL working reliably on an AMD RX480 with this release. On 6 and 7 some OpenCL kernels would consistently fail with illegal instruction problems. If you've been using AMDGPU PRO just for OpenCL support, and prefer running mainline drivers, give AMDGPU a try on llvm8 and a recent kernel.

xvilka 8y ago

While they did an amazing job on improving the framework, compiler, and tools, a few important compatibility features weren't addressed: - '-MT' and '-MM' options support (like in GCC)[1] - '-M'/'-MF' options support (like in GCC)[2] - 'MENUEX' menu resource section parsing (like in MSVC)[3] Also, we recently found a problem[4] while compiling radare2 with 8.0.0 clang-cl for Windows. Hopefully, it will be addressed soon since the tool offers sanitizers support for the Windows platform, which is a blast. [1] https://bugs.llvm.org/show_bug.cgi?id=10091 https://bugs.llvm.org/show_bug.cgi?id=10091 [2] https://bugs.llvm.org/show_bug.cgi?id=8312 https://bugs.llvm.org/show_bug.cgi?id=8312 [3] https://bugs.llvm.org/show_bug.cgi?id=40108 https://bugs.llvm.org/show_bug.cgi?id=40108 [4] https://bugs.llvm.org/show_bug.cgi?id=41128 https://bugs.llvm.org/show_bug.cgi?id=41128

deleted 8y ago

[deleted]

xvilka 8y ago

I should also note that KLEE 2.0 was released[1] in line with LLVM 8.0 release. It is the first release in the last 2 years, so the amount of changes is huge. If you are using symbolic execution - I recommend you to check out this version. [1] https://github.com/klee/klee/releases/tag/v2.0 https://github.com/klee/klee/releases/tag/v2.0