[Bug gcov-profile/114751] New: .gcda:stamp mismatch with notes file

["gejoed at rediffmail dot com" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114751

            Bug ID: 114751
           Summary: .gcda:stamp mismatch with notes file
           Product: gcc
           Version: 11.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: gcov-profile
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gejoed at rediffmail dot com
  Target Milestone: ---

Hi team,

In my org project we use gcc/gcov which is customised by another team. However
with version 11.4.0 we did see a '.gcda:stamp mismatch with notes file' while
running gcov tool. The same command goes fine with the previous branch code
which uses gcc 10.3.0. 

Example would be like :
<toolchain-path>/gcov -l src-file.c -o ./src-file-obj-dir-path

src-file.gcda:stamp mismatch with notes file
File 'src-file.c'
Lines executed:0.00% of 36
Creating 'src-file.c.gcov'

File '../../abcd/ef/hijk.h'
Lines executed:0.00% of 2
Creating 'src-file.c##hijk.h.gcov'

File '../include/lmno.h'
Lines executed:0.00% of 2
Creating 'src-file.c##lmno.h.gcov'

Lines executed:0.00% of 40

This is seen for several files in the new branch of code where gcc v11.4.0 is
used and not seen with older branch where the gcc version is 10.3.0.

We generate the gcov based image (compiled with --coverage in CFLAGS) , load
the image on the device, do testing, collect gcda files from device and put it
back in the same obj-dir location and run the gcov tool to get the gcov files
(eg :src-file.c.gcov).

We checked the time stamp of gcda vs gcno files and even then the issue was
seen. Was there any specific enhancement with 11.x version which would be
causing the issue or is there any further check to be done during the
compilation with --coverage or during the gcov tool run ?

Due to my organisation restriction, I'm not able to give more info on the file
names used and the make file info but I can try the best to get the info for
your understanding. 
Awaiting valuable reply. 

Thank you team for your support always !