News for hackers. Stuff that matters.
Re:When an implementation monoculture might be the right thing by pietroglyph on Friday June 01, 2018 @01:03AM (#17202734)
This article specifically references not having to deal with cross-compiler differences as a monoculture advantage. So there are _differences_, perhaps not incompatibilities.
Re:When an implementation monoculture might be the right thing by camgunz on Friday June 01, 2018 @01:36AM (#17202839)
OP is pretty light on details, but GCC and clang keep up with standards amazingly well (who knows about MSVC). I'm sure there are bugs, but what even are they? Is there a list? It's definitely not at all like the difference between Python and Jython, or even Python 2 and 3.

Or if you want an even better example, look at JS benchmarks for different kinds of loops. Every engine is different. How completely bananas is that. Differences like these are a whole other universe compared to differences in the major C++ compilers.

Re:When an implementation monoculture might be the right thing by sanxiyn on Friday June 01, 2018 @03:58AM (#17203438)
The post addresses this. To quote:

> A fair amount of work has been done to deal with peculiar bugs in all three compilers: you can go search the source code and/or Bugzilla to find hacks that were needed for one reason or another.

So go search the source code and/or Bugzilla. Treasures await!

Re:When an implementation monoculture might be the right thing by camgunz on Friday June 01, 2018 @05:10PM (#17210347)
So I searched [1] Bugzilla and found 51 issues, none of which are from the last 2 years. There really just isn't an issue with GCC/clang incompatibility with the standard.

The issues that are still open [2] are practically all either a dev didn't test with GCC and got away with things they shouldn't have in clang, or dealing with Apple's ancient version of GCC.

I think this "monoculture" thing is really about MSVC being not that great, which I sympathize with, and which everyone who's ever used MSVC for C or C++ has discovered. But that shouldn't be an excuse to stop using GCC, which is an excellent compiler and has been for generations.

[1] https://bugzilla.mozilla.org/buglist.cgi?short_desc=gcc&reso...

[2] https://bugzilla.mozilla.org/buglist.cgi?quicksearch=gcc

Re:When an implementation monoculture might be the right thing by JdeBP on Friday June 01, 2018 @06:02AM (#17203963)
Bat-Ulzii Luvsanbat claims to know about MSVC.

* https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcin...