News for hackers. Stuff that matters.
Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by jhasse on Wednesday February 12, 2020 @05:54PM (#22313699)
It's bad for GCC, but good for C++ developers. GCC and MSVC will die and there will be only one compiler on all platforms (which is also the best one).

Just have a look at Chrome and Firefox. They already use Clang on all platforms. On Windows they are working on replacing link with lld. Android has deprecated GCC completely. In the future it's gonna be clang + lld + libc++ all the way. And yeah, GDB and WinDbg will also be replaced by LLDB.

Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by zelly on Thursday February 13, 2020 @12:53AM (#22315604)
> GDB and WinDbg will also be replaced by LLDB

This is the longest shot of what you mentioned. I can see a future where the llvm toolchain dominates but people still use GDB because of muscle memory. (Unless LLDB changes its commands to match GDB.)

Also GCC is guaranteed to live for at least 50 yrs because of freetards. GNU has die hard users and developers who would rather die than leave. LLVM has money, big money. It remains to be seen which matters more.

Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by littlestymaar on Thursday February 13, 2020 @02:54AM (#22316078)
> GCC and MSVC will die and there will be only one compiler on all platforms

That sounds like bad for C++ developers: competition is what made clang as good as it is now, and GCC improved a lot since Clang's threat happened. Also, Clangs bugs would become the de facto standard (this is happening right now on the web with Chrome).

Monocultures are harmful…

Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by jhasse on Monday February 17, 2020 @04:58AM (#22346607)
Competition is good, sure. But focusing the limited developing resources on one compiler, too. Without parallel universes it's hard to know what actually leads to a better compiler.
Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by voldacar on Wednesday February 12, 2020 @08:54PM (#22314675)
GCC still generates faster binaries (on average across a wide set of benchmarks) than clang as of last year
Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by big_chungus on Wednesday February 12, 2020 @10:16PM (#22315051)
Not that much faster. Most benchmarks find that GCC is a little ahead, but not much:

https://www.phoronix.com/scan.php?page=article&item=gcc9-cla...

https://medium.com/@alitech_2017/gcc-vs-clang-llvm-an-in-dep...

Remember that these are both Linux benchmarks; GCC on windows is a bit sketchy with MinGW. Things can usually be made to work, but Clang is the only real competitor to MSVC (unless you're counting Intel's crazy-expensive offering, which is not intended for general use).

Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by loeg on Wednesday February 12, 2020 @09:31PM (#22314833)
Better debuginfo (still), too.
Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by Santosh83 on Wednesday February 12, 2020 @11:46PM (#22315392)
If there is only one of something then it makes no sense to say it is the best... that's one reason why monopolies lead to worsening quality.