Slashdot Mirror
Chromium Being Ported To VC++, Scrubbed of Compiler Bugs
jones_supa writes: Moving a big software project to a new compiler can be a lot of work, and few projects are bigger than the Chromium web browser. In addition to the main Chromium repository, which includes all of WebKit, there are over a hundred other open-source projects which Chromium incorporates by reference, totaling more than 48,000 C/C++ files and 40,000 header files. As of March 11th, Chromium has switched to Visual C++ 2015, and it doesn't look like it's looking back. The tracking bug for this effort currently has over 330 comments on it, with contributions from dozens of developers. Bruce Dawson has written an interesting showcase of some VC++ compiler bugs that the process has uncovered. His job was to investigate them, come up with a minimal reproduce case, and report them to Microsoft. The Google and Microsoft teams get praise for an excellent symbiotic relationship, and the compiler bugs have been fixed quickly by the Visual Studio team.
Can't see anything but your reflection..
This comment was written with the intention to opt out of advertising.
As near as I can tell they switched the Windows build from VC++ old version to VC++ new version. Because:
- Improved C++11/14 support /analyze checked rolled into main compile
- Security improvements
- Some
- Possibly some improved support for "cloud" builds
All compilers have 'weird bugs and stuff' - staying with compilers 'that are well support across all platforms' is another matter altogether. I'm not sure why you are asserting the fact that VC++ has bugs - your text reads as if you are trying to convey it's the only compiler that does contain bugs, therefore you can't fathom as to why on earth a development team would move from one dev platform to another because of the bugs. Because it's Microsoft, it must be shit right? That's what you're saying?
Just their principal Windows build environment changed in March 2016 from VS 2013 (still supported) to VS 2015. This is no news... really.
Chrome is not an application. It is an entire operating system, that just happens to include a browser. Think of it as ChromeOS VM.
A lot of times compiler bugs fall into categories that aren't bugs at all. 1. Stuff that people think is standard C, but it's really a GCC-ism. 2. Stuff people didn't know about standard C, such as the order of argument evaluation being unspecified. 3. Default settings on one compiler being forgiving and/or handling uninitialized variables in a particular way, and the other compiler not being so forgiving.
I can't remember who said so first, but it's generally given that the first people to scream "compiler bug" are usually doing something wrong with their code. I wouldn't be surprised if a lot of the people in academia who you say write shitty software are doing that kind of thing. "Oh! compiler bug!" Nope. You just had something that "worked on my machine" and now it doesn't.
Chrome is not an application. It is an entire operating system, that just happens to include a browser.
How does it compare to emacs?
It's GUI-based instead of ncurses-based
Moderate advantage to Chrome on that one, I think.
and is scripted with Javascript instead of Lisp.
Err, we'll call that one a draw.
>"As of March 11th, Chromium has switched to Visual C++ 2015..."
This should have been written as: ..."
"As of March 11th, WINDOWS Chromium build has switched supported compilers FROM Visual C++ 2013 TO Visual C++ 2015
This has nothing to do with OSX or linux builds and is not that much important news.