== This Week ==
* Livermore Loops - Test was badly adapted, failures were due to undefined behaviour - Removed from test-suite until a propper adaptation can be done - LTO and Static Analysis issues raised - http://llvm.org/bugs/show_bug.cgi?id=14851 - http://llvm.org/bugs/show_bug.cgi?id=14852
* LLVM Builds - Builds fine on Chromebook, same check-all failures as other ARM targets - test-suite fails, haven't had time to properly investigate - Getting a pandaboard to act as a buildbot - Creating a LAVA job to run often and on-demand internally
* AArch64 in LLVM - reviewing lots of patches from ARM (Tim Northover) - full back-end just sent, will review over the weekend
* Loop Vectorize - Some discussions with Tao Wang about cost models - Got some ideas on what are the best changes for LLVM's cost model - Not much on this front
* EuroLLVM 2013 - Trying to define the level of sponsorship Linaro can provide - CFP will go out next week, committee created, conference confirmed
* Commits http://llvm.org/viewvc/llvm-project?view=rev&revision=171642 http://llvm.org/viewvc/llvm-project?view=rev&revision=171859
== Next Week ==
* Get the LAVA job running - need account at people.linaro.org, RT created * Get at least one buildbot in sync with LLVM's lab * Get some traction on the cost model * Cambridge LLVM Social, liaise with ARM
== Future ==
* Try to draft an LLVM story for Linaro (and understand why I'm here in the first place) ;) * Have builds with vectorization turned on
On 11 January 2013 18:55, Renato Golin Linaro renato.golin@linaro.org wrote:
== This Week ==
- Livermore Loops
- Test was badly adapted, failures were due to undefined behaviour
- Removed from test-suite until a propper adaptation can be done
- LTO and Static Analysis issues raised
- http://llvm.org/bugs/show_bug.cgi?id=14851
- http://llvm.org/bugs/show_bug.cgi?id=14852
- LLVM Builds
- Builds fine on Chromebook, same check-all failures as other ARM targets
- test-suite fails, haven't had time to properly investigate
- Getting a pandaboard to act as a buildbot
- Creating a LAVA job to run often and on-demand internally
- AArch64 in LLVM
- reviewing lots of patches from ARM (Tim Northover)
- full back-end just sent, will review over the weekend
- Loop Vectorize
- Some discussions with Tao Wang about cost models
- Got some ideas on what are the best changes for LLVM's cost model
- Not much on this front
- EuroLLVM 2013
- Trying to define the level of sponsorship Linaro can provide
- CFP will go out next week, committee created, conference confirmed
- Commits
http://llvm.org/viewvc/llvm-project?view=rev&revision=171642 http://llvm.org/viewvc/llvm-project?view=rev&revision=171859
== Next Week ==
- Get the LAVA job running
- need account at people.linaro.org, RT created
ci.linaro.org is more appropriate.
- Get at least one buildbot in sync with LLVM's lab
- Get some traction on the cost model
- Cambridge LLVM Social, liaise with ARM
== Future ==
- Try to draft an LLVM story for Linaro (and understand why I'm here in the
first place) ;)
- Have builds with vectorization turned on
On 12 January 2013 06:57, Fathi Boudra fathi.boudra@linaro.org wrote:
- need account at people.linaro.org, RT created
ci.linaro.org is more appropriate.
people.linaro.org was recommended by Dave, probably for the general purpose + cron jobs.
But if ci.linaro.org is more appropriate, I might ask that, too.
thanks, --renato
On 01/12/2013 05:49 AM, Renato Golin Linaro wrote:
On 12 January 2013 06:57, Fathi Boudra <fathi.boudra@linaro.org mailto:fathi.boudra@linaro.org> wrote:
> - need account at people.linaro.org <http://people.linaro.org>, RT created ci.linaro.org <http://ci.linaro.org> is more appropriate.people.linaro.org http://people.linaro.org was recommended by Dave, probably for the general purpose + cron jobs.
But if ci.linaro.org http://ci.linaro.org is more appropriate, I might ask that, too.
That was probably a bad recommendation by me. I thought you were just wanting some one-off job for personal interest. In that case a cron job would work. However, if you have something more official then Fathi is right - you should use ci.linaro.org.
On 13 January 2013 06:51, Andy Doan andy.doan@linaro.org wrote:
That was probably a bad recommendation by me. I thought you were just wanting some one-off job for personal interest. In that case a cron job would work. However, if you have something more official then Fathi is right - you should use ci.linaro.org.
Hi Andy,
For now, I'm still getting my head around LAVA and trying to spawn a job at it. Any machine that is not turned off when I'm cycling back home would do. ;)
In the long run, I'd like to add the LLVM tests as LAVA supported tests, so that anyone can run out-of-the-box on any new hardware at any time.
cheers, --renato
linaro-toolchain@lists.linaro.org
-
Andy Doan -
Fathi Boudra -
Renato Golin Linaro