[Bug testsuite/111298] time-profiler-2.c flaky on glibc RISC-V with qemu

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW
 Target|riscv   |riscv aarch64
   Last reconfirmed||2023-11-27

--- Comment #4 from Andrew Pinski  ---
Confirm, I see this also on aarch64.

[Bug testsuite/111298] time-profiler-2.c flaky on glibc RISC-V

[amylaar at gcc dot gnu.org via Gcc-bugs]

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

Jorn Wolfgang Rennecke  changed:

   What|Removed |Added

 CC||amylaar at gcc dot gnu.org

--- Comment #3 from Jorn Wolfgang Rennecke  ---
(In reply to Patrick O'Neill from comment #0)
> I'm guessing that this is likely due to some conflict between
> time-profiler-1.c and time-profiler-2.c and filing this under testsuite
> framework issue, but feel free to move it if it's likely caused by a
> specific component.

My guess is that the atomic fetch-and-update emitted by
gimple_gen_time_profiler
is not actually atomic (at least under RISC-V Qemu).
Note that in time-profiler-2.c, there is a parent and a child process that
access the same gcov data.

[Bug testsuite/111298] time-profiler-2.c flaky on glibc RISC-V

[patrick at rivosinc dot com via Gcc-bugs]

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

--- Comment #2 from Patrick O'Neill  ---
Yep I'm using qemu-user, thanks for the link.

[Bug testsuite/111298] time-profiler-2.c flaky on glibc RISC-V

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #1 from Andrew Pinski  ---
Are you testing using qemu-user?

If so it has always been flaky:
https://gcc.gnu.org/pipermail/gcc-patches/2013-November/377091.html