On 07/22/16 07:46, Martin Liška wrote:
Hi.
As described in the PR, current numbering scheme in gcov-io.h would overflow in
couple of years.
Thus, I'm suggesting to switch from:
[major][minor/10][minor%10][release_status]
to:
[major/10][major%10][minor][release_status]
If I'm reading that right, although we'll have a strange collating order that
won't match release ordering, we won't get collisions (because the minor version
never got above 9).
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Yes thanks. I was wondering when gcc's new version numbering would impact this
ident.
nathan
