On Mon, Mar 09, 2020 at 08:05:41PM +0100, Martin Husemann wrote: > On Mon, Mar 09, 2020 at 02:49:23PM -0400, Greg Troxel wrote: > > I am not really following the issue, but I don't understand why what the > > default C++ sublanguage is matters. It would seem that behavior should > > be correct for any --std passed to compilers, per that sublanguages's > > specification, and what you get by default is just what happens to you > > if you don't pass --std. (And I basically think a build that does not > > pass an explicit --std is buggy, but that's a separate issue.) > > The problem is that this c++ lib does not support compiling with -std= > for standards < C++11 (IIUC).
This isn't even true. libc++ generally tries to provide a working C++03 implementation, but assumes partial C++11 support for ABI reasons. Joerg
