(Probably informal) The toolchain is available in Ubuntu and Linaro Android, and as an community option in a range of other build systems. Discuss Yocto support.

Joint session between kernel and toolchain working groups to discuss options to improve the kernel debugging experience.

We're planning to support KVM on A15. This session is to discuss the QEMU parts of this. It's engineering-focused and QEMU-focused (the more general discussion and aspects which cut across different Linaro and external teams will be done in a different session).

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Profile guided optimisation is where you run a program, collect data on how it actually runs, then use that to make a further optimised build. We'd like to use PGO as a theme in a future quarter but need to investigate PGO and the potential gains first. Discuss.

Most distributions build at a medium optimisation level but a fair bit of our work is enabled at -O3. Discuss the current status, benchmark results, arguments to justify, and areas that need work.

We'd like to use Firefox as a toolchain testsuite and a benchmark. Discuss approach, existing testsuites, and the parts to benchmark. I would like to check if these workloads are the interesting ones? Load and rendering of a good set of web pages JavaScript Start up of browser Shutdown of browser Imaging - or are we covered by EEMBC DENBench, ConsumerBench Input data that can be redistributed? I would like to hear the views on this and understand how to proceed. Can Mozilla share the tp5 pages? Is it necessary that the content is redistributed, or can it be internal to the tcwg? How to proceed with cross-compiling? I would like to use a multistrap/xdeb approach, but it seems hard. Is it OK to create a chroot with everything installed, zip it up and reuse it for some months? Configuring the build for different flags and features Should we use .mozconfig, myRules.mk, and myConfig? If debian package is used for building, can myrules and myconfig still be used? Which benchmark(s) to choose for browsing? ARMBBench EEMBC BrowsingBench Talos with a set of pages Would it be possible to integrate ARMBBench or EEMBC BrowsingBench in the Talos framework? System level testing What are the plans for system level? Is there an overlap? Can we benfit, work together... When done, should the toolchain browsing benchmark tests be run in LAVA?

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups

Afternoon engineering and hacking session for Toolchain and OCTO Working Groups