You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PGO: compiler warnings for source files with no profile data #117804
PGO builds do not generated profile data for all source files. This means that for a PGO build, you may end up with compiler warnings for source files with no profile data. Do we want to silence these warnings? If we do, it may be harder to spot if PGO builds fail to include profile data correctly.
It's one of these cases where if we suppress them once, we'll forget about coverage entirely, which is worse than simply continuing to not fix it (someone might be motivated to fix it in the future if they see it)
Activity
erlend-aasland commentedon Apr 12, 2024
Example warning:
zooba commentedon Apr 12, 2024
Unless they're actually disruptive (breaking builds), I'd rather leave them there by default.
Seems easy enough to add the suppression to CFLAGS manually, yeah? Should we just doc it?
zooba commentedon Apr 12, 2024
It's one of these cases where if we suppress them once, we'll forget about coverage entirely, which is worse than simply continuing to not fix it (someone might be motivated to fix it in the future if they see it)
erlend-aasland commentedon Apr 12, 2024
I would be fine with that.
pythongh-117804: Document how to suppress PGO unprofiled source warnings
gh-117804: Document how to suppress PGO unprofiled source warnings (#…
pythongh-117804: Document how to suppress PGO unprofiled source warni…
[3.12] gh-117804: Document how to suppress PGO unprofiled source warn…
pythongh-117804: Document how to suppress PGO unprofiled source warni…