* Setting up laptop, desk, mailing lists, SSH keys, Launchpad, etc

 * Livermore Loops Benchmark

   * It fails on some types of builds but not others

   * Failure is due to LTO, problem identified, trying to get a reduced case

 * Getting LLVM building nightly and running the test-suite

   * Got where we are with ARM and others regarding buildbots

   * LLVM compiles and checks on pandaboard, need test-suite

   * Got a Chromebook to run the test-suite

 * LLVM web presence (pages, svn repositories, etc) dead

== Next Week ==

 * Reduce the LTO bug on Livermore kernels

   * Report it once I have more information and a reduced case

   * Try to fix it

 * Checkout Zorg (LLVM's build system integrator)

   * Force builds to use LNT (new test harness, which passes)

   * Someone else is looking into setting up consistent LTO tests to the rest already

 * Get Ubuntu on Chromebook and build LLVM on it + test-suite

   * Understand the CBuild infrastructure and setup a board to do it automatically

   * Revise the current LLVM build to be continuous and check-all

 * Help Nadav Rotem (Apple) with the cost model for vectorization on ARM VFP/NEON

 * Meeting with ARM and "le French" to finalize the EuroLLVM 2013 and send the CFP

== Future ==

 * Validate vectorization for ARM after cost model is reasonably accurate

   * Vectorization will be turned on by default as of 3.3 on -O2 or higher

   * Reduced strength with -Os, but still on

 * Make Livermore Loops vectorize

   * Allow vectorization to detect global structures as safe

   * Allow floating point vectorization if using -unsafe-math

 * Plan a workflow to report / fix bugs that our internal CBuild finds on ARM

 * Liaise with ARM on what processes can be shared / commoned-up

 * Try to be less verbose on activity reports...