On 6/17/21 3:59 AM, Eugene Rozenfeld wrote:
|The commit from this patch (https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=23eb66d1d46a34cb28c4acbdf8a1deb80a7c5a05) changed the semantics of gcov_read_string and gcov_write_string. Before this change the string storage was as described in gcov-io.h: "Strings are padded with 1 to 4 NUL bytes, to bring the length up to a multiple of 4. The number of 4 bytes is stored, followed by the padded string." After this change the number before the string indicates the number of bytes (not words) and there is no padding. Was this file format change intentional?
Hello. Thanks for heads up! Yes, the change was intentional and I'm going to update documentation entry in gcov-io.h.
It breaks AutoFDO because create_gcov produces strings in the format specified in gcov-io.h. Thanks, Eugene
Sure, that needs to be adjusted. Martin
