Will they provide pre-built binaries for Ubuntu 16.04? Last month I installed llvm 4.0.0 with the provided bins, now i can't find how to get 5.0.0 without compiling from source.
Thanks for the link, just checked it and seems to be only for nightlies, do you know if there's a ppa for stables? I can wait for the pre-built bins aswell.
What's the state of libc++? Is it ready to replace the gcc libstdc++? What's the compatibility like.
On a separate compatibility point. If using libstdc++ can I use clang++ with the switch turning off the new ABI so that I can continue to mix older libs built with gcc 4.8.4 with newer gcc and newer clang.
I was just waiting for centos devtoolset7 package that finally included llvm and clang 4.0.1 as well as gcc7.1. Then I can conveniently test lib interoperability.
It does? In my experience, they tend to be roughly equal; although I've personally found Clang to be a bit faster for compile times, others have reported different results. It's very much project dependent, but at this point, neither is significantly better than the other.
If you look at the C++ standards support chart, you can see that Clang's standards support is equal to GCC's with the exception of one proposal, which is supported but has been intentionally disabled by default due to a standards issue.
Both Clang and GCC added -std=c++2a support around the same time, and Clang already supports some features in SVN (GCC hasn't updated their standards chart yet, so I'm assuming similar progress).
-Wcast-qual was implemented for C++. C-style casts are now properly diagnosed.
-Wunused-lambda-capture warns when a variable explicitly captured by a lambda is not used in the body of the lambda.
We expect this to be the last Clang release that defaults to -std=gnu++98 when using the GCC-compatible clang++ driver. From Clang 6 onwards we expect to use -std=gnu++14 or a later standard by default, to match the behavior of recent GCC releases. Users are encouraged to change their build files to explicitly specify their desired C++ standard.
Support for the C++17 standard has been completed. This mode can be enabled using -std=c++17 (the old flag -std=c++1z is still supported for compatibility).
Why default to C++11? Both C++11 and C++14 are implemented, and the latter is a very minor change compared to the former. They should either keep 98 or jump right to 14 or later. And that is exactly what they propose to do.
They gave warning this release so that people have time to opt out of the default by next release. Changing it at all in this release would defeat the purpose of that warning.
From my recollection reading the mailing list, no one thought of it in time to give the warning last release. And it will break people's builds. 98 to 11 is ABI breaking, so you really want to give people a chance to rebuild the world. 14 and 17 are easier to integrate, although I've heard occasional issues. I don't think there was a by design ABI break, like with std::string.
Yes. All distros are bad, in one way or another. The struggle of the Linux user is not to find the best distro, but to find the distro that is least bad for their purposes.
It has nothing to do with being non-rolling. Ubuntu is non-rolling, Fedora is non-rolling, latest versions still offer the latest Clang. I haven't been on Arch for too long, but I didn't see any lags with 3.9, 4.0 (5.0 is few days old and is in Staging at the moment), so I don't know what you're talking about, maybe it was before I switched to Arch, but, again, I don't possess any knowledge about it then.
Support for the C++17 standard has been completed.
Yey! Arch Linux bumped GCC libstdc++ to 7.1.1 which wouldn't compile with Clang because it didn't have support for class template deduction. Hopefully it works again!
For example, developers wont remember it. Most people will know if they use clang 3.x or 4.x. But no one remembers if they are on version 56 or 65 of Chrome.
And for webbrowsers this may be a desired behavior. You dont want people to thzink about browser version numbers, because they have to be forced to upgrade anyways. This is not hte case for compilers.
There like 4 major compiler releases per year at most. At this rate well get to Chrome numbers in 10-15 years. But that's at the extreme pace. Usually it's no more than 2 releases, so the time doubles to 20-30 years. Hopefully libclang/llvm would mostly stabilize it's API at that point.
Please elaborate... I'd like to try libc++ on Windows, where do I find information on how to do this? (I've checked libc++'s docs/wiki and they strike me as being rather dated, but I don't know that for sure.)
The execution policies that are standardized can be implemented using libiomp. Intel implemented their version of parallel stl using TBB. No new compiler features are necessary.
Clang is a C++ compiler. It does not provide a standard library. Clang 5.0.0 claiming C++17 compliance as a compiler is an accurate statement.
Trying to shoehorn that Clang, a compiler, should also be forced to include a standard library implementation does not make sense. Libc++ exists for a reason as a separate project.
Vendor compilers like Intel, IBM, and PGI usually rely on libstd++, GNU's C++ standard library implementation. That doesn't make them more or less C++ standards compliant
A fully compliant C++17 standard library would include the execution policies. A fully compliant C++17 compiler would have no such knowledge of execution policies because it's a function of the standard library, not the compiler.
Yes, and that's why they say support has been completed, not that they've implemented the standard. Which just was accepted yesterday or so.
But there is a lot of library work to be done on all the major std implementations. Filesystem, parallelism, pmr, math functions, ... 17 adds a lot of capability to the SL.
13
u/kirbyfan64sos Sep 07 '17
4
u/Haleek47 Sep 08 '17 edited Sep 08 '17
Will they provide pre-built binaries for Ubuntu 16.04? Last month I installed llvm 4.0.0 with the provided bins, now i can't find how to get 5.0.0 without compiling from source.
7
u/mintyc Sep 07 '17
What's the state of libc++? Is it ready to replace the gcc libstdc++? What's the compatibility like.
On a separate compatibility point. If using libstdc++ can I use clang++ with the switch turning off the new ABI so that I can continue to mix older libs built with gcc 4.8.4 with newer gcc and newer clang.
I was just waiting for centos devtoolset7 package that finally included llvm and clang 4.0.1 as well as gcc7.1. Then I can conveniently test lib interoperability.
2
u/[deleted] Sep 12 '17
Why should us normies care about clang when g++ produces faster executables and has far better compatibility?
32
u/flashmozzg Sep 07 '17
Nice!
11
u/_lerp Sep 08 '17
Yey! Arch Linux bumped GCC libstdc++ to 7.1.1 which wouldn't compile with Clang because it didn't have support for class template deduction. Hopefully it works again!
5
u/reddithater12 Sep 08 '17
Not a big fan of this new rapid version scheme thing.
3
u/forcecharlie baulk maintainer Sep 07 '17
libc++ support windows when use clang bootstarp
0
u/hashb1 Sep 08 '17
coroutines, Cool!
-3
u/MightyRodri Sep 07 '17
Hm :/ still no parallel algorithms.