> > This will become more common problem for multithreaded profiles where > > one needs to annotate locking and busy waiting loops in them for example > > (or the scheduler responsible for executing paralle tasks). > > > > I can see this to be practically achievable but we probably want to > > produce some guidelines for doing that and probably teach gcov-tool to > > compare profiles and say to which degree they match (i.e. which > > functions match for each of levels of reproducibility). > > > > The problem is that profiles are continuous and the errors too, but > > optimizaitons looks for certain thresholds, so small errors may lead to > > code changes, so I think our current method of looking at relatively few > > packages and patching errors when they appear is not very good long term > > strategy... Especially if it makes us to drop useful transformations by > > default with -fprofile-use and no additional option. > > To be honest we have very few packages that use PGO in openSUSE:Factory.
We should aim to have more :) > > Anyway, are you fine with the suggested? What exactly is suggested? Honza > > Thanks for discussion, > Martin
