The March/April C++ meeting was back in Kona, Hawaii again, only a year and a half after the last Kona meeting. As usual, Red Hat sent three of us to the meeting: Jonathan Wakely, Torvald Riegel, and me.
Continue reading “Red Hat at the ISO C++ Standards Meeting (April 2017, Kona): Core Language”
It was quite a trek to get to Oulu, Finland for the June 2016 C++ Standards Committee meeting, but we were warmly received and the meeting went well once we arrived. We had very pleasant weather most of the week, and it was fun to experience the midnight sun, even though it played havoc with my sleep schedule.
The main order of business at this meeting was to vote on a first Committee Draft (CD) of the (expected) C++17 standard, ideally with as much as possible of the work that has been moving through the pipeline. The Core and especially the Library working groups were very effective at moving through their workload of papers at this meeting: Core ended the week with no papers left to review, and Library got through ~50 papers and had only two left at the end.
As usual, the committee divided into multiple working groups: the primary groups that met throughout the week are Core language, language Evolution, Library, Library Evolution, and Parallelism/Concurrency (SG1). Also as usual, I spent the week in the Core language working group.
In my report on the Jacksonville C++ Meeting last February, I described various proposals that were working through the committee. Of the core language features I listed there as expected or hoped to make it into C++17 at this meeting, almost all did. Note that as of this writing the final revisions of the adopted papers have not been posted publicly yet, but the links should adjust when they are.
Continue reading “Red Hat at the ISO C++ Standards Meeting (June 2016, Oulu): Core Language”
There were three of us from Red Hat at the C++ meeting in Jacksonville, FL back in February, and it seems I never posted my trip report. So here it is now.
This was a fairly eventful meeting, as we’re rapidly approaching C++17 and so the big question on everyone’s minds was “What’s going to make it in?” In the end, many things did, but not Concepts, which some had been hoping for as a headline item.
We started and finished the week looking at the list of Technical Specifications that we were considering incorporating into C++17.
Continue reading “Jacksonville C++ Core Language Meeting Report”
Red Hat sent four engineers to the spring C++ meeting this year, in Lenexa, Kansas, a suburb of Kansas City. It was hosted by Perceptive Software, a division of Lexmark. The meeting went very smoothly overall; while there were some disagreements they were pretty cordial.
The first disagreement came up during the Monday evening session when Bjarne was talking about his vision of C++17. He wants to see multiple big new features, lest people get bored with C++ after another relatively minor update like C++14. Google representatives and Herb Sutter (the Convener) pointed out that what they’ve been hearing from users is that they’re happier than ever with C++, and use of C++ has been increasing on available metrics, so what we’ve been doing seems to be working. Personally, I’m happy to continue with Herb’s plan to do regular releases with whatever happens to be ready at the time, much like GCC releases.
Continue reading “Lenexa C++ Meeting Report (Core Language)”
Fedora 22 will ship with GCC 5, which brings a whole host of enhancements, among which is a new default C++ ABI. In this article, we’ll cover how that ABI transition will work in Fedora.
Background – what’s an ABI, why is it changing, and what does this mean for developers?
Put simply, binary compatibility means applications that are compiled on a combination of an operating system and a particular hardware architecture will load and run similarly across different instances of the operating environment. Application binaries consist of executable files and Dynamic Shared Objects (DSOs – the formal name for shared libraries), and the level of compatibility is defined by a specific application binary interface (ABI).
Continue reading “GCC 5 in Fedora”
The GNU C++ team works hard to avoid breaking ABI compatibility between releases, including between different -std= modes. But some new complexity requirements in the C++11 standard require ABI changes to several standard library classes to satisfy, most notably to std::basic_string and std::list. And since std::basic_string is used widely, much of the standard library is affected.
Many users routinely rebuild all their code when they change compilers; such users will be unaffected by this change. Code built with an earlier compiler will also continue to work with the new libstdc++, which provides both old and new ABIs.
Continue reading “GCC5 and the C++11 ABI”
The Red Hat toolchain team was well-represented at the Fall 2014 meeting of the standardization committee (JTC1/SC22/WG21) in Urbana-Champaign, IL, USA. In this article, Jason Merrill summarizes the main highlights and developments of interest to Red Hat Enterprise Linux developers. Stay tuned for separate articles summarizing the library and concurrency working group aspects.
The fall meeting of WG21 (the C++ standardization committee) this year was hosted by the CS department at the University of Illinois at Urbana-Champaign. This was the first meeting after ratification of the C++14 standard, and we weren’t changing the working paper while C++14 was out for voting ISO doesn’t allow changes to the working paper while there’s an open ballot, so there was a lot of leftover business from the last few meetings that was waiting to be voted on.
As usual, I spent the week in the Core Language Working Group. We spent the majority of the week reviewing papers for new language features.
Continue reading “Red Hat at the ISO C++ Standards Meeting (November 2014): Core”