[Webkit-unassigned] [Bug 94665] Baseline optimizer should try to optimize per-port if global optimization fails
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Aug 22 09:20:31 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=94665
--- Comment #5 from Brady Eidson <beidson at apple.com> 2012-08-22 09:20:28 PST ---
(In reply to comment #4)
> No, chromium has always tried to match the mac baselines where possible. There are two reasons for this: first, the Chromium mac port was explicitly trying to match the Apple Mac port. Second, it's simply the case that we produce a lot of the same baselines (thousands, last I checked), and so there's a significant advantage to sharing.
>
> That said, you're not doing anything wrong. The tools are simply busted; if they were working correctly you'd be able to rebaseline to your heart's content and we'd simply adjust automatically.
>
> It may also be that if fixing the tools turns out to be hard, we should stop falling back to mac and just accept the duplicated baselines, but I don't think we're quite there yet.
Thanks for the explanation!
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list