On 01/31/2013 10:37 AM, Nicholas Nethercote wrote:
On Thu, Jan 31, 2013 at 3:03 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote:
Given the above, I'd like to propose the following long-term solutions:
1. Disable PGO/LTCG now.
2. Try to delay disabling PGO/LTCG as much as possible.
3. Try to delay disabling PGO/LTCG until the next time that we hit the
limit, and disable PGO/LTCG then once and for all.
In the long run, 1 and 3 are the same. If we know we're going to turn
it off, why not bite the bullet and do it now?
Because we're still missing plenty of optimizations in our code
to be fast in microbenchmarks. It would be quite huge pr loss if we suddenly
were 10-20% slower in benchmarks.
But we're getting better (that last spike is because bz managed to effectively
optimize out one test).
http://graphs.mozilla.org/graph.html#tests=[[73,1,1]]&sel=none&displayrange=365&datatype=running
Has anyone run other than dromaeo? Peacekeeper perhaps?
-Olli
One big advantage of
that is that we'd immediately stop suffering through PGO-only bugs.
(I'm not necessarily advocating this, BTW, just observing that the two
options are basically equivalent.)
Also, stupid question time: is it possible to build on Windows with
GCC and/or clang?
Nick
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
