public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "myron.walker at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/94928] New: Doc comments in gcov-io.h do not show cwd and unexec blocks in the Notes file format Date: Sat, 02 May 2020 22:09:11 +0000 [thread overview] Message-ID: <bug-94928-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928 Bug ID: 94928 Summary: Doc comments in gcov-io.h do not show cwd and unexec blocks in the Notes file format Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: myron.walker at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- The documentation of the notes file format below do not show the cwd or unexec_blocks data items. note: unit function-graph* unit: header int32:checksum string:source function-graph: announce_function basic_blocks {arcs | lines}* announce_function: header int32:ident int32:lineno_checksum int32:cfg_checksum string:name string:source int32:start_lineno int32:start_column int32:end_lineno basic_block: header int32:flags* arcs: header int32:block_no arc* arc: int32:dest_block int32:flags lines: header int32:block_no line* int32:0 string:NULL line: int32:line_no | int32:0 string:filename When you look at the gcov.c file, you can see that at the beginning of the notes file right after the stamp, there is an item for cwd and unexec blocks. bbg_stamp = gcov_read_unsigned(); bbg_cwd = xstrdup(gcov_read_string()); <<<<< Not documented bbg_supports_has_unexecuted_blocks = gcov_read_unsigned(); <<<<<< Not documented There also is a missing int32:artificial that should be between the function name and function source file. function_name = xstrdup(gcov_read_string()); unsigned artificial = gcov_read_unsigned(); <<<< Not documented unsigned src_idx = find_source(gcov_read_string());
next reply other threads:[~2020-05-02 22:09 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-02 22:09 myron.walker at gmail dot com [this message] 2020-05-04 5:38 ` [Bug gcov-profile/94928] " marxin at gcc dot gnu.org 2020-05-06 9:14 ` marxin at gcc dot gnu.org 2020-05-06 13:13 ` myron.walker at gmail dot com 2020-05-06 13:17 ` marxin at gcc dot gnu.org 2020-05-06 13:31 ` myron.walker at gmail dot com 2020-05-06 13:38 ` marxin at gcc dot gnu.org 2020-05-06 13:52 ` myron.walker at gmail dot com 2020-05-06 13:59 ` marxin at gcc dot gnu.org 2020-05-06 14:04 ` marxin at gcc dot gnu.org 2020-05-06 14:14 ` myron.walker at gmail dot com 2020-05-06 14:21 ` marxin at gcc dot gnu.org 2020-05-06 14:57 ` myron.walker at gmail dot com 2020-05-06 15:22 ` myron.walker at gmail dot com 2020-05-07 7:35 ` marxin at gcc dot gnu.org 2020-05-07 10:41 ` myron.walker at gmail dot com 2020-05-07 11:17 ` marxin at gcc dot gnu.org 2020-05-07 13:37 ` myron.walker at gmail dot com 2020-05-11 7:22 ` marxin at gcc dot gnu.org 2020-05-11 7:26 ` cvs-commit at gcc dot gnu.org 2020-05-11 8:06 ` marxin at gcc dot gnu.org 2020-05-11 14:45 ` myron.walker at gmail dot com 2020-05-11 18:36 ` marxin at gcc dot gnu.org 2020-05-11 19:05 ` myron.walker at gmail dot com 2020-05-13 13:38 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-94928-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).