This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
gcov and initialized data
- From: "taylor, david" <David dot Taylor at dell dot com>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Cc: "taylor, david" <David dot Taylor at dell dot com>
- Date: Thu, 3 May 2018 17:09:08 +0000
- Subject: gcov and initialized data
I want to use gcov in an embedded type environment. It supports both cold boot
and warm boot.
For warm boot it does not reload the program from media, instead it 'just' jumps
to the start and begins again. Due to support for warm boot, it does not support
read-write initialized data. Writable data is initialized at run-time.
When you build your program for code coverage (-ftest-coverage -fprofile-arcs),
GCC creates some initialized read-write GCOV related data. Has anyone modified
GCC to, presumably either under control of a command line option or possibly a
configure time option, to initialize such data at run-time instead of compile-time?
Thanks.
David
p.s. In case it matters / anyone cares -- we have copyright assignments on file for
GCC, BINUTILS, and GDB, which the company lawyers assure me survived our
acquisition by Dell.