https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> So that I can decide whether I am allowed to do things totally randomly
> or if I must follow some sort of seeded determinism.
That is almost always the wrong approach really.
Just assume the seed it always set and then use the seed as given. Don't ever
do something non-determinstic if you can avoid it. GCC has changed away from
that years ago.
The randomness in GCC is only needed to get unique symbol names across two
translation units which might have the same file name. The seed is there so you
can set it to get the same symbol across builds if you know if the file names
are unique in the first place.
The coverage.cc is a non-issue as libgcov will do the right thing as mentioned.
