Exactly what control do we have over what gets PGOed? In particular:

1) Are we able to exclude particular object files or libraries from PGO
when we link libxul, reducing PGO memory usage for the final link? I think
you said "yes" on IRC.

2) Are we able to collect a set of object files, link them with PGO into a
static library, and then link the result into libxul, reducing PGO memory
usage for the final link?

Given the answer to #1 is yes, I think it's worth going through the
contents of libxul and disabling PGO on stuff that we deem unimportant. If
the answer to #2 is yes, we can independently-PGO those bits to limit the
perf hit.

Rob
-- 
Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to