On Tue, Mar 6, 2012 at 6:54 AM, Andy Doan andy.doan@linaro.org wrote:
I don't think that's a problem. In fact, what I'm suggesting is to simply have it available as a download from our NAS system in the lab, that is behind the firewall and not exposed. You'll need to get us to put the file there, but then it wouldn't need to be behind yet another layer of security.
The problem is that its not just a single file. I need one file per toolchain we'd like to compare. So for coremark we might have: coremark-android4.4.3, coremark-linaro4.5, coremark-linaro4.6-2012-01, coremark-linaro4.6-2012-02. Additionally, people might also be interested in experimenting with one-off type build configurations. So we need some mechanism to instruct the LAVA test (coremark.py) which binary it should be using.
Given the permutations, and that this will at least change monthly, I thought it would be nice to not depend on having to get some file(s) update in the validation lab.
And you want to run a batch against existing compilers, and run variants such as -O2 vs -O3 against the same compiler.
-- Michael