(In reply to comment #25) > Following up on the Linaro Toolchain list[1], I found out a few facts: > > 1. This feature was implemented in GCC and libstdc++ in 2012, after > discussions on the cauldron with distro representatives.
No. It was implemented in April this year, shortly before the gcc-5 release. I've pointed out compatibility issue immediately: https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00153.html
> 2. The feature is poorly documented, and may have changed behaviour until > recently. I have no evidence of changes, is anyone does, please update.
The were no behavioral changes at all after that patch went in.
> 3. The problem only started because distros have chosen GCC 5 as their > default compilers for the current releases, which defaults to C++11.
No gcc-5 doesn't default to C++11 and the issue here has nothing to do with C++98 vs. C++11.
Please try to get the facts strait, before posting long misleading replies.
(In reply to comment #25)
> Following up on the Linaro Toolchain list[1], I found out a few facts:
>
> 1. This feature was implemented in GCC and libstdc++ in 2012, after
> discussions on the cauldron with distro representatives.
No. It was implemented in April this year, shortly before the gcc-5 release. /gcc.gnu. org/ml/ gcc-patches/ 2015-04/ msg00153. html
I've pointed out compatibility issue immediately:
https:/
> 2. The feature is poorly documented, and may have changed behaviour until
> recently. I have no evidence of changes, is anyone does, please update.
The were no behavioral changes at all after that patch went in.
> 3. The problem only started because distros have chosen GCC 5 as their
> default compilers for the current releases, which defaults to C++11.
No gcc-5 doesn't default to C++11 and the issue here has nothing to do with
C++98 vs. C++11.
Please try to get the facts strait, before posting long misleading replies.