On 12/02/14 14:52, Michael Eager wrote:
As Cary said, the values are not fixed until the spec is released.
As Jason said, the values are unlikely to change.
Fair enough.
The standards process can be a bit messy at times, particularly
when we realize that something we added to a draft needs to be changed.
We try to avoid making unnecessary changes, naturally. On the other
hand, we don't want something in an internal draft of the DWARF
specification to prevent us from making necessary changes.
Understood. And I don't want GCC handcuffing the DWARF standardization
process or generally making things harder for you.
The most conservative approach is to wait for the DWARF Version
5 spec to be released. While there is no guarantee that attribute
values will not change in the final spec, the risk if this happening
seems small.
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.
As I mentioned, Jason and Jakub have the final say on including this
stuff into gcc-5 -- I just wanted to see if there was a way we cooperate
better with the DWARF committee on this class of issues.
Thanks,
jeff
