Comment # 7 on bug 1040589 from Richard Biener

Honza, are you aware of any issue regarding reproducability of the final .gcda
files when merging results of multiple invocations?  IIRC we use file-locking
to serialize the update but of course different parallel program invocations
might result in random order of merging.  How can that ever be an issue?  Maybe
for counter overflows?  or some ordering of items and then rippling down
effects when the profile is read by -fprofile-use?