I've set up a new user on my laptop that we can use for experimenting with benchmarks during Connect. Here's what we've got: * A user called 'connect' * Ramana, Ulrich, Åsa, and myself can log in via SSH * bzr repo for trunk, 4.6, and gcc-linaro 4.6 * Tarballs of all gcc-linaro 4.4, 4.5, and 4.6 releases * Tarballs of the recent CSL, Google 4.6, and Android 4.4 compilers * A sysroot in ~/sysroot * Cross-binutils etch in ~/cross * A shared ccache in ~/ccache primed with these * A ~/env.sh that sets up the right paths etc * A ~/builds/doconfigure.sh that configures for our standard ARMv7-A C/C++/Fortran configuration * EEMBC, DENBench, and SPEC 2000 under ~/benchmarks
The trees under build/ build into build/$ver/build and install into build/$ver/install.
The benchmarks are set up to cross build and cross run. I've pulled ursa2 out of the farm and nuked it, so we can do something like: make CROSS_COMPILE=arm-linux-gnueabi- RUN="$PWD/sshrun ursa2"
to run the benchmarks.
I'll see about perf. We still need to re-baseline the benchmarks and get perf traces.
Anything else needed?
You can log in and try things if you want. Go through the bounce host and try connecting as connect@crucis.
-- Michael
Hi Michael,
On 2 February 2012 02:44, Michael Hope michael.hope@linaro.org wrote:
I've set up a new user on my laptop that we can use for experimenting with benchmarks during Connect. Here's what we've got: * A user called 'connect' * Ramana, Ulrich, Åsa, and myself can log in via SSH
works for me .
* bzr repo for trunk, 4.6, and gcc-linaro 4.6
Ack.
* Tarballs of all gcc-linaro 4.4, 4.5, and 4.6 releases * Tarballs of the recent CSL, Google 4.6, and Android 4.4 compilers * A sysroot in ~/sysroot * Cross-binutils etch in ~/cross * A shared ccache in ~/ccache primed with these * A ~/env.sh that sets up the right paths etc * A ~/builds/doconfigure.sh that configures for our standard ARMv7-A C/C++/Fortran configuration
I've put a copy of some of the directory names and info from this mail into a common top level file called README.where just as I was looking around.
I've poked around a bit but not tried building anything serious as I wasn't sure if it would affect your laptop in any other way.
* EEMBC, DENBench, and SPEC 2000 under ~/benchmarks
I haven't tried running any of these but I presume that should fine.
The trees under build/ build into build/$ver/build and install into build/$ver/install.
The benchmarks are set up to cross build and cross run. I've pulled ursa2 out of the farm and nuked it, so we can do something like: make CROSS_COMPILE=arm-linux-gnueabi- RUN="$PWD/sshrun ursa2"
Are you carrying ursa2 as well with you or are we running this remotely from connect ?
cheers Ramana
I'm bringing ursa2.
-- Michael
On Fri, Feb 3, 2012 at 12:51 PM, Ramana Radhakrishnan ramana.radhakrishnan@linaro.org wrote:
Hi Michael,
On 2 February 2012 02:44, Michael Hope michael.hope@linaro.org wrote:
I've set up a new user on my laptop that we can use for experimenting with benchmarks during Connect. Here's what we've got: * A user called 'connect' * Ramana, Ulrich, Åsa, and myself can log in via SSH
works for me .
* bzr repo for trunk, 4.6, and gcc-linaro 4.6
Ack.
* Tarballs of all gcc-linaro 4.4, 4.5, and 4.6 releases * Tarballs of the recent CSL, Google 4.6, and Android 4.4 compilers * A sysroot in ~/sysroot * Cross-binutils etch in ~/cross * A shared ccache in ~/ccache primed with these * A ~/env.sh that sets up the right paths etc * A ~/builds/doconfigure.sh that configures for our standard ARMv7-A C/C++/Fortran configuration
I've put a copy of some of the directory names and info from this mail into a common top level file called README.where just as I was looking around.
I've poked around a bit but not tried building anything serious as I wasn't sure if it would affect your laptop in any other way.
* EEMBC, DENBench, and SPEC 2000 under ~/benchmarks
I haven't tried running any of these but I presume that should fine.
The trees under build/ build into build/$ver/build and install into build/$ver/install.
The benchmarks are set up to cross build and cross run. I've pulled ursa2 out of the farm and nuked it, so we can do something like: make CROSS_COMPILE=arm-linux-gnueabi- RUN="$PWD/sshrun ursa2"
Are you carrying ursa2 as well with you or are we running this remotely from connect ?
cheers Ramana
linaro-toolchain@lists.linaro.org
-
Michael Hope -
Ramana Radhakrishnan