Re: [cfe-users] Should clang++ -g produce debugging info for all types?

2019-07-25 Thread David Blaikie via cfe-users
No, it shouldn't - clang attempts to avoid emitting duplicate debug info across the program (it assumes you built the whole program and all libraries with debug info), gcc assumes the same thing though in slightly different/fewer ways. The solution is to install the -dbg build of your libstdc++ pa

[cfe-users] Should clang++ -g produce debugging info for all types?

2019-07-25 Thread Bob Eastbrook via cfe-users
On Fedora 30, "clang++ -g main.cc" does not emit debugging information for types such as std::string. I can only get complete debugging information by including "-fno-limit-debug-info". On Ubuntu 19.04, "clang++ -g" emits debugging info for std::string as expected. Which behavior of "-g" is corr

Re: [cfe-users] clang-cl choosing VC++ backend on Windows

2019-07-25 Thread Hans Wennborg via cfe-users
On Mon, Jul 22, 2019 at 3:29 PM Edward Diener via cfe-users wrote: > > Given multiple installations installed of Visual Studio/VC++ on Windows, > with none of them normally in the PATH, how does clang-cl choose which > one to use at compile/link time as the clang backend ? It's a bit involved. Yo