C++ Weekly Episode 43: Stack Elision?—Jason Turner
Episode 43 of C++ Weekly.
Stack Elision?
by Jason Turner
About the show:
In this episode Jason explores Clang's and GCC's ability to elide stack operations during optimization.
March 11-13, Online
March 16-18, Madrid, Spain
March 23-28, Croydon, London, UK
March 30, Kortrijk, Belgium
May 4-8, Aspen, CO, USA
May 4-8, Toronto, Canada
C++ Meetup with Bjarne Stroustrup
May 9, Florence, Italy
June 8 to 13, Brno, Czechia
June 17-20, Folkestone, UK
September 12-18, Aurora, CO, USA
November 6-8, Berlin, Germany
November 16-21, Búzios, Rio De Janeiro, Brazil
By Adrien Hamelin | Jan 3, 2017 01:48 PM | Tags: efficiency community
Episode 43 of C++ Weekly.
Stack Elision?
by Jason Turner
About the show:
In this episode Jason explores Clang's and GCC's ability to elide stack operations during optimization.
By Adrien Hamelin | Jan 3, 2017 01:40 PM | Tags: community
A very interesting plugin for our blogs:
A new way of blogging about C++
by Yehonathan Sharvit
From the article:
This blog post is about to show a new way of blogging about C++.
Look at a typical blog post about C++: The post usually presents a couple of code snippets. As I see it, there are two pains with code snippets:
- they contain the input and the output but not the actual evaluation of the input
- it’s impossible for the reader to modify the output...
By Adrien Hamelin | Dec 30, 2016 03:16 PM | Tags: experimental community
An interesting point of view and implementation of a variant in one article!
My take on variant
by Jonathan Müller
From the article:
C++17 is going to add std::variant. To quote the linked documentation, it is a “type-safe union”. A union is like a struct, but can only store one member at a time. This has many applications, but sadly it doesn’t mix well with non-trivial types, you have to call the destructor yourself etc. Furthermore, nothing prevents you from accessing a union member that isn’t active.
std::variant fixes that. It correctly calls the destructor when switching the active member, it prevents invalid access, etc. However, I’m not quite happy with it and I needed an implementation now. So I’ve decided to implement my own variant as part of my type_safe library.
It was a fun challenge and since my previous attempt was two years ago, I could improve it a lot. Let’s go through some of my design decisions.
By Adrien Hamelin | Dec 30, 2016 02:47 PM | Tags: performance community
Who did not measure wrongly?
Heap fragmentation or how my micro-benchmark went wrong
by David Gross
From the article:
Micro-benchmarking code always looks simple: a few variables, a small for loop and two std::chrono calls. I think this simplicity is an illusion. Micro-benchmarking is either complicated or inaccurate...
By Adrien Hamelin | Dec 29, 2016 01:50 PM | Tags: community boost
A new version is out!
Boost 1.63.0
By jdgarcia | Dec 29, 2016 10:58 AM | Tags: community
Daniel Garcia reports from the recent std::cpp conference:
Conference Report
by Daniel Garcia
From the report:
Last November 24th we had the fourth edition of using std::cpp, our annual spanish conference on C++ for professional developers. The conference is a one-day free event held every year at University Carlos III of Madrid, in Leganés. We had around 200 registered attendees (most of them professional developers).
We would like to share some answers from the evaluation questionaries:
- 75% of attendees were professional developers, 14% were students, and 11% were academics.
- 92% declared they use regularly C++.
- The most popular version of C++ was C++11 (73%), followed by C++98/03 (63%) and C++14 (21%). Note that you could vote for more than one. However, no one declared to make use of any extension or TS.
- Most popular compiler was gcc (60%), followed by Microsoft (57%), and clang++ (14%).
- When we asked for domains a found a split among multiple sectors: telco (20%), aerospace/naval (11%), civil engineering (9%), bank/finance/insurance (7%), developer tools (7%), videogames (6%), research/academia (4%), transport (4%), industrial manufacturing (2%).
By Adrien Hamelin | Dec 26, 2016 03:07 PM | Tags: community basics
How to return well:
Return early and clearly
by Arne Mertz
From the article:
There are different guidelines out there about where and how many return statements to use in a function, e.g. return only once at the end of the function or return early and often. Which one makes for the most readable code?
By Meeting C++ | Dec 16, 2016 10:48 AM | Tags: video performance intermediate experimental efficiency community c++14 c++11 boost basics advanced
A week full of video editing brings the first batch of Meeting C++ 2016 videos online:
More videos are online!
by Jens Weller
Meeting C++ 2016 Playlist
From the article:
With today, almost all videos from the A and all videos of the D Track are online. There is a recording issue with one talk in the A track, which might get resolved in 2017. Also since today, the Meeting C++ YouTube channel has more then 400k views!
The full video set you can find in the Meeting C++ 2016 Playlist, the newest videos are easily found by visiting the Meeting C++ YouTube channel or subscribing to this RSS feed.
By Meeting C++ | Dec 1, 2016 09:17 AM | Tags: community
The monthly list of upcoming C++ User Group meetings:
C++ User Group meetings in December
by Jens Weller
From the article:
In total its already 30 groups which are meeting, also there are 10 new groups since the last posting:
Minsk, London, Melbourne, Karlsruhe, Ulm (Qt), San Diego, Belgrade, Luxembourg, Dallas FW, Plano.
By Adrien Hamelin | Nov 29, 2016 02:14 PM | Tags: experimental community
C++17 makes a new step.
Trip Report: C++ Standards Meeting in Issaquah, November 2016
by Botond Ballo
From the article:
Last week I attended a meeting of the ISO C++ Standards Committee (also known as WG21) in Issaquah, Washington (near Seattle). This was the third and final committee meeting in 2016; you can find my reports on previous meetings here (February 2016, Jacksonville) and here (June 2016, Oulu), and earlier ones linked from those. These reports, particularly the Oulu one, provide useful context for this post...