> In both section bodies "int" follows the section's compact flag (varint when > compact, big-endian otherwise), as for other section bodies.
It's not clear to me why we need both compact and non compact, or what the trade offs between the two are and why would the user decide for one or another. Is varint worth it? Normally the files are not that big anyways. Or is it significantly slower? If there is no big difference perhaps it can be always used. If the goal is just smaller files could always store them compressed with a standard library. But I haven't seen a case where the size of the gcov (as opposed to the perf.data) was a problem. IIRC one issue that made files bigger with the old autofdo is that it saved zero counts, but perhaps that is already fixed. Also why do we bother with endian conversion? It seems like unnecessary complexity. Maybe I missed it, but it would be good to have a separate spec for the file format.
