On Dec 3, 2014, at 1:18 PM, Jeff Law <l...@redhat.com> wrote: > The problem is that waiting for the final spec means effectively GCC doesn't > support the feature until gcc-6 in 2016 just due to the expected timing of > the dwarf5 standard and the gcc release schedule. They pretty much couldn't > line up much worse in this regard.
So, I’d recommend implementing the draft so that we can get a feel for if it is done, if we like it, if there is anything else that needs to be fixed about it and review of the draft. We can not default to generation of dwarf5 until it is a standard. Not unreasonable to default to dwarf4 if people prefer that. Advanced users that want the draft, with the understanding it isn’t set in stone, can ask for it by -gdwarf5. I view this is largely the same as a language standard. Implement early, implement often, as the standard comes out, you have already implemented it, had adventuresome users comment on it; had vendors build worlds with it, fixed all the bugs found, then you can just flip the switch. I don’t favor waiting until a standard is published before implementing it.
