On 3/30/22 16:48, Sebastian Huber wrote:
On 30/03/2022 15:30, Sebastian Huber wrote:
On 30/03/2022 13:56, Martin Liška wrote:
Example:
base64 -d log.txt | gcov-tool merge-stream
The gcov-tool uses a new tag which contains the filename of the associated gcov
info file:
gcov-dump b-xilinx_z
On 30/03/2022 15:30, Sebastian Huber wrote:
On 30/03/2022 13:56, Martin Liška wrote:
Example:
base64 -d log.txt | gcov-tool merge-stream
The gcov-tool uses a new tag which contains the filename of the
associated gcov info file:
gcov-dump b-xilinx_zynq_a9_qemu/init.gcda
b-xilinx_zynq_a9_q
On 30/03/2022 13:56, Martin Liška wrote:
Example:
base64 -d log.txt | gcov-tool merge-stream
The gcov-tool uses a new tag which contains the filename of the
associated gcov info file:
gcov-dump b-xilinx_zynq_a9_qemu/init.gcda
b-xilinx_zynq_a9_qemu/init.gcda:data:magic `gcda':version `B20 '
b
On 3/28/22 18:23, Sebastian Huber wrote:
On 24/03/2022 13:03, Martin Liška wrote:
On 3/24/22 11:51, Sebastian Huber wrote:
Maybe we could add the file path into the gcov information stream using a new
tag:
#define GCOV_TAG_GCDA_FILE_NAME ((gcov_unsigned_t)0xa500)
Then the complete gcov
On 24/03/2022 13:03, Martin Liška wrote:
On 3/24/22 11:51, Sebastian Huber wrote:
Maybe we could add the file path into the gcov information stream
using a new tag:
#define GCOV_TAG_GCDA_FILE_NAME ((gcov_unsigned_t)0xa500)
Then the complete gcov information can be dumped using a single b
On 3/24/22 11:51, Sebastian Huber wrote:
Maybe we could add the file path into the gcov information stream using a new
tag:
#define GCOV_TAG_GCDA_FILE_NAME ((gcov_unsigned_t)0xa500)
Then the complete gcov information can be dumped using a single base64 encoded
stream. We could add some s
On 24/03/2022 11:29, Martin Liška wrote:
On 3/23/22 15:50, Sebastian Huber wrote:
The attached script reads the log file and creates the *.gcda files
using gcov-tool. Initially, the target files do not exist.
Now I've got your use-case and I like it. It's cool one can utilize GCOV
even withou
On 3/23/22 15:50, Sebastian Huber wrote:
The attached script reads the log file and creates the *.gcda files using
gcov-tool. Initially, the target files do not exist.
Now I've got your use-case and I like it. It's cool one can utilize GCOV even
without a filesystem.
Please update the patch.
Hello Martin,
On 23/03/2022 13:19, Martin Liška wrote:
On 3/23/22 10:34, Sebastian Huber wrote:
Hello.
Thanks for the patch. Note we're in stage4, so the patch can eventually go
in in the next stage1.
ok, good.
The gcov_profile_merge() already had code to deal with profile
information
wh
On 3/23/22 10:34, Sebastian Huber wrote:
Hello.
Thanks for the patch. Note we're in stage4, so the patch can eventually go
in in the next stage1.
The gcov_profile_merge() already had code to deal with profile information
which had no counterpart to merge with. For profile information from fil
The gcov_profile_merge() already had code to deal with profile information
which had no counterpart to merge with. For profile information from files
with no associated counterpart, the profile information is simply used as is
with the weighting transformation applied. Make sure that gcov_profile
11 matches
Mail list logo
