Currently there is no reasonable way to control the warnings in the 'use' phase of the IRPGO pass. This is problematic because the output can be somewhat spammy. This patch adds some flags which allow us to optionally disable these warnings. The current upstream behavior will remain the default.
Question : do you get warnings when there is no source change? This indicates some potential bugs in compiler. If you see them, can you help file bugs?
Great, if possible Sean or David could you commit this for me? I don't have
As for your question. Sean and I have actually experienced warnings
resulting from a difference in inlining choices in different TU's but we
will definitely be bringing this up very soon as a separate discussion.
These flags were mostly to deal with instrprof_error::unknown_function
which for our use case tends to be pretty spammy but not very helpful.
It's good to add options to control the warning -- sometime there are just too many warnings.
But I would suggest to separate this from the stats collection. This patch disables it altogether with the message.
The meaning/name of the flags have been changed so that we only pass them to disable the warnings. The flags also no longer interfere with the statistics.