Linaro Toolchain Benchmarks

Firefox as a toolchain benchmark

Registered by Asa Sandahl

Set up a working cross-compilation environment for Firefox. Do a first benchmark. Present the results to the group and evaluate if the results/findings are useful.

If Firefox is too hard for cross-compiling, then switch to a WebKit based browser: Chromium or QtWebKit.
Investigate if Mozilla can share their test content (tp5 test pages) with Linaro. Investigate if the TryServer and Selenium are useful for this work.

References:
Michael Edwards' tool for cross compilation: https://github.com/mkedwards/crosstool-ng
Mozilla build instructions: https://developer.mozilla.org/En/Developer_Guide/Build_Instructions
TryServer: https://wiki.mozilla.org/ReleaseEngineering/TryServer
Selenium: http://seleniumhq.org/projects/remote-control/

Blueprint information

Status:
Complete
Approver:
Michael Hope
Priority:
Low
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
milestone icon backlog
Started by
Michael Hope
Completed by
Matthew Gretton-Dann

Related branches

Sprints

Whiteboard

We now have v8 as a benchmark. Lowering Firefox.

[2013-08-22 matthew-gretton-dann] This is a system level benchmark, and so not on TCWG's target list currently.

(?)

Work Items

Work items:
Build Firefox natively on a Panda and verify that the program works: TODO
Investigate how to use the Qt backend in Firefox and decide if to use it: TODO
Use the rootfs from the Panda as sysroot for cross-compiling: TODO
Investigate how to use crosstool-ng: TODO
Run one benchmark using browsers built with different toolchains: TODO
Analyze results: TODO
Report in LAVA: TODO
Talk to Clint Talbert about the tp5 pages: TODO
Investigate the Selenium Remote Control test suite for automation: TODO
Investigate if TryServer could be used for Linaro: TODO

This blueprint contains Public information 
Everyone can see this information.