LLVM 8.0 Released With Cascade Lake Support, Better Diagnostics, More OpenMP/OpenCL (phoronix.com)
After being delayed for the better part of one month, LLVM 8.0 officially is finally available. From a report: LLVM release manager Hans Wennborg announced the release a few minutes ago and summed up this half-year update to LLVM and its sub-project as: "speculative load hardening, concurrent compilation in the ORC JIT API, no longer experimental WebAssembly target, a Clang option to initialize automatic variables, improved pre-compiled header support in clang-cl, the /Zc:dllexportInlines- flag, RISC-V support in lld. And as usual, many bug fixes, optimization and diagnostics improvements, etc."
I was curious what WebAssembly was, so I hunted down an FAQ.
Summary is that WebAssembly is a binary format to use in place of Javascript, to avoid parsing time.
Really happy to see LLVM carry on, what a great project!
"There is more worth loving than we have strength to love." - Brian Jay Stanley
concurrent compilation in the ORC JIT API
Finally. For years, we've had ELFs in our binaries and I'm very happy that ORCs now have their own API.
8 of 13 people found this answer helpful. Did you?
and corporate sponsored 'oversights'.
I was just having a discussion the other day where I was cussing out gcc, which got into a discussion of cussing out clang, and then a generation discussion cussing out C++, glibc, and a variety of major design fuckups that continued for years.
Hell, go read the rationale for gcc-6.5.0 having a MAJOR ABI REGRESSION left in it despite being the last stable release of the gcc6 series 'Well, we want people to move to GCC 7 anyways.' I've read similar reasoning from clang devs.
It's time for any greybeards left who hate incompatibilities and regressions to start showing some leadership and teach these beardlings a thing or two. If you don't things are only going to continue getting worse as these people become elders like yourselfs, only with much of the old and none of the wiser.
This is amusing timing for me personally because I've just been compiling Qt 5.12.2, and after configuring I'm getting a message saying the location of LLVM must be in my system PATH, which is a new message for 5.12.2. I then went to Slashdot and saw this article.
I'm still not sure what it is, but it seems I'll now have to look into it.
> LLVM 8.0 Released With Cascade Lake Support
I came to read about luxurious hand-made travel bags and italian full-carbon racing bicycles, but all people talk about here is just "coding" activity? What's going on?
LLVM is a set of compiler toolchain components, it is used to provide the middle tier of a compiler system for many languages. It's written in C++
Well you can have your grey beard C complier that is compatible back to 1892 or your can have your blazingly fast, full featured AST interface that you can imbed into IDEs. Iâ(TM)m honestly frustrated C++ standards have lagged years behind every other modern language. With PyPy standard python will soon be as fast as C++, with full introspection, user friendly meta programming, none of the horrific 10000 line compiler errors for a missing comma or mismatched type due to a over or under dereferenced variable. Grey beards need to trim that beard and throw the cheesy poofs they were saving in it since 1974 out.
You're a naive clueless dipshit. So typical of the "programmers" that exist everywhere nowdays. No clue what they're doing. Don't even understand how a fucking computer and operating system works.
And how many of those 10,000+ SSNs belong to programmers who will translate my C program into machine code by hand?
With PyPy standard python will soon be as fast as C++, with full introspection, user friendly meta programming, none of the horrific 10000 line compiler errors ...
Right, with python you get type errors in run time instead. Enjoy your application crashing at run time because object "foo" does not have property "baz".
The release note does not seem to mention OpenMP or OpenCL. The release note does not contain the string "OpenMP" or the string "OpenCL". Am I missing something obvious? What has actually changed in that regard?
Got 380% usage on my four core system today, and it was pretty easy coding too.
Keep up the excellent work!
Stop it! Just stop it, ok? STOP!
as an old, old UNIX 'cc' user, seeing a toolchain with a /Zc:dllexportInlines- flag makes me want to kill myself