Android NDK: GCC is now deprecated, everyone should be switching to Clang

jdlyga wrote: post #2

Perhaps for Android, but I'm hesitant about using Clang for Win64 due to some recent bugs (such as tellg not working correctly).

NDK is only for Android (as in a C++ toolchain for Android, the toolchain runs on Windows, Linux and Mac but the resulting executables are meant for Android) ... what do you mean with Win64 in this context ?

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#5

Post by vvpan » Mon, Dec 21, 2015, 9:24 PM UTC

The title is a bit misleading. It is deprecated in the context of that project. Meaning they personally won't support it anymore. It's not deprecated in general as a compiler.

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#6

Post by klodolph » Mon, Dec 21, 2015, 9:28 PM UTC

jdlyga wrote: post #2

Perhaps for Android, but I'm hesitant about using Clang for Win64 due to some recent bugs (such as tellg not working correctly).

That's probably a bug in libc++, not Clang. They're under the same roof, but different people work on them.

Also, I would mock you for using at all but you've probably got legacy code just the same as I do.

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#7

Post by xd1936 » Mon, Dec 21, 2015, 9:30 PM UTC

AlexeyBrin wrote: post #4

jdlyga wrote: post #2

Perhaps for Android, but I'm hesitant about using Clang for Win64 due to some recent bugs (such as tellg not working correctly).

NDK is only for Android (as in a C++ toolchain for Android, the toolchain runs on Windows, Linux and Mac but the resulting executables are meant for Android) ... what do you mean with Win64 in this context ?

He probably meant the x64 compiler on Windows.

From the link: "Also note that Clang packaged in the Windows 64 NDK is actually 32-bit."

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#8

Post by psibi » Mon, Dec 21, 2015, 9:35 PM UTC

For someone not following the project, what's the reason for deprecation and switch over to LLVM ?

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#9

Post by haroldp » Mon, Dec 21, 2015, 9:38 PM UTC

bracewel wrote: post #3

waits for RMS to get mad https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html

> I would guess they describe their work as "open source" and do not talk about freedom.

Wow, what an asshole. Maybe they consider legal restrictions on how other people may use their software to be the opposite of freedom? Maybe that is the truth and maybe RMS has a good point to make, but how tone deaf is to call anything that isn't GNU, "unfree"? To suggest that they don't even talk about freedom because their license is a little different? What an asshole.

Re: Android NDK: GCC is now deprecated, everyone should be switching to Clang

#10

Post by Buge » Mon, Dec 21, 2015, 9:39 PM UTC

klodolph wrote: post #6

jdlyga wrote: post #2

Perhaps for Android, but I'm hesitant about using Clang for Win64 due to some recent bugs (such as tellg not working correctly).

That's probably a bug in libc++, not Clang. They're under the same roof, but different people work on them. Also, I would mock you for using at all but you've probably got legacy code just the same as I do.

I'm curious, what's wrong with iostream?