== Progress ==
* TCWG-447 (5/10)
* Re-spin few versions of the patches and posted after testing based
on reviews.
* http://gcc.gnu.org/ml/gcc-patches/2014-04/msg01743.html
* http://gcc.gnu.org/ml/gcc-patches/2014-04/msg01744.html
* TCWG-413 Spec2006 (5/10)
* Updated the scripts to deploy libraries and to run cross spec
benchmarking with them.
* Experimented with open embedded image generation for benchmarking-
still finding some issues even with a trusty chroot.
* Started benchmarking and variance analysis.
== Plan ==
* Benchmarking.
* Upstream zero/sign extension elimination activities.
* Start with literal pool merging.
Very short week (3 half days)
== Progress ==
* GCC trunk cross-validation (2/10):
- monitored results, and reported some regressions/new fails
- moved away from Jenkins
- as commit rate has decreased, there is no backlog in validations
* Neon-intrinsics test (1/10):
- Continuing conversion for inclusion in the GCC testsuite.
- Preparing an additional Makefile, simpler than the current one,
to help using the testsuite for various GCC variants until
conversion is complete.
== Next ==
* Continue to closely monitor GCC trunk validations
* Neon intrinsics tests
* Off Thursday/Friday
Short week, Labor day (2/10)
== Issues ==
* None
== Progress ==
* Launchpad bugs: (4/10)
o LP #1307197 : gcc-4.9 miscompiles linux kernel zlib for armv3
- This an LRA issue for architectures < armv4 withi movhi
- Investigation ongoing
o LP #1169164 : including signal.h exposes various PSR_MODE #defines
- The proposed patch fix the issue
- Still need some validation before upstream submission
* Test new backport workflow and Cbuild2 (2/10)
- Some troubles to access the build farm.
* Misc:
o Cbuildv1 baby-sitting (1/10)
o Various meetings (1/10).
== Next ==
- Two days off
- FSF branch merge + backports
== Issues ==
* None
== Progress ==
* May 1-2: Laybor day holiday
* Commit fcsel support patch for aarch64 @r209889.
* Tuning move-loop-invariants heuristics for -fira-loop-pressure:
- Record register pressure for each invariant other than a max for all.
- Take register pressure into account when selecting the best candidate.
== Plan ==
* Tuning move-loop-invariants heuristics
* Ping pending patches.
== Planned leaves ==
* June 2.
* -fno-sched-interblock
* loop-inv
> Hello,
> I have a problem building gcc-linaro-arm-linux-gnueabihf
> toolchain for my x86_64 system. I download crosstool-ng (v1.13) and
> toolchain source code (4.8-2014.03) from
> http://releases.linaro.org/14.03/components/toolchain/binaries. I use
> the example configuration linaro-arm-linux-gnueabihf (obtained from
> ct-ng list-samples) and modify some entries using menuconfig option,
> like the local tarballs directory (pointing to downloaded toolchains
> source code directory) and the prefix directory (custom directory output).
>
> This is the problem during the execution of "ct-ng build" command:
>
> =================================================================
>
> [INFO ] Installing final compiler
>
> [EXTRA] Configuring final compiler
>
> [EXTRA] Building final compiler
>
> [EXTRA] AFMOYA: EMPIEZA A EJECUTARSE make jobsflags all
>
> [EXTRA] -j5
>
> [EXTRA] /home/afmoya/Descargas/build/.build/arm-linux-gnueabihf/build/build-cc
>
> [ERROR] configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
>
> [ERROR] make[2]: *** [configure-zlib] Error 1
>
> [ERROR] make[1]: *** [all] Error 2
>
> [ERROR]
>
> [ERROR] >>
>
> [ERROR] >> Error happened in: main[scripts/crosstool-NG.sh]
>
> [ERROR] >>
>
> [ERROR] >> For more info on this error, look at the file: 'build.log'
>
> [ERROR] >> There is a list of known issues, some with workarounds, in:
>
> [ERROR] >> '/opt/cross-linaro/share/doc/ct-ng-linaro-1.13.1-4.8-2014.03/B - Known issues.txt'
>
> [ERROR]
>
> [ERROR] Build failed in step 'Extracting and patching toolchain components'
>
> [ERROR]
>
> [ERROR] (elapsed: 11:18.57)
>
> make: *** [build] Error 2
>
>
> Highlighted in green some entries added for me in attemp to understand
> the execution secuence.
>
> The error is triggered in the "configure-zlib" target of
> "${CT_TOP_DIR}/.build/arm-linux-gnueabihf/build/build-cc/Makefile". The
> "configure.log" of the
> "${CT_TOP_DIR}/.build/arm-linux-gnueabihf/build/build-cc/zlib/"
> directory shows some errors (I don't know if the are significants):
>
> LINE 83: Thread model: posix
>
> LINE 84: gcc version 4.7.2 (Debian 4.7.2-5)
>
> LINE 85: configure:3234: $? = 0
>
> LINE 86: configure:3223: x86_64-build_unknown-linux-gnu-gcc -V >&5
>
> LINE 87: gcc: error: unrecognized command line option '-V'
>
> LINE 88: gcc: fatal error: no input files
>
> LINE 89: compilation terminated.
>
> LINE 90: configure:3234: $? = 4
>
> LINE 91: configure:3223: x86_64-build_unknown-linux-gnu-gcc -qversion >&5
>
> LINE 92: gcc: error: unrecognized command line option '-qversion'
>
> LINE 93: gcc: fatal error: no input files
>
> LINE 94: compilation terminated.
>
> ...
>
> LINE 188: configure:6661: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
>
> LINE 189: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>
> LINE 190: compilation terminated.
>
> ...
>
> LINE 207: configure:6720: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
>
> LINE 208: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
>
> LINE 209: compilation terminated.
>
> ...
>
> LINE 318: configure:10852: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
>
> LINE 319: conftest.c:23:28: fatal error: ac_nonexistent.h: No such file or directory
>
> LINE 320: compilation terminated.
>
> Some idea of what's the problem?
>
> This is my system info:
> Linux afmoya-pc 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
>
> and some tools version installed in my system:
> gcc (Debian 4.7.2-5) 4.7.2
> GNU Make 3.81
> GNU Awk 4.0.1
> ...
>
> Best regards:
> Alexis Fajardo Moya.
I have removed the "zlib" folder from "gcc-linaro-4.8-2014.03.tar.xz" tarball, the compiler is also using zlib-1.2.5 statically linked, and thats permit compile the Linaro toolchain.
Best regards
Lic. Reinier Millo Sánchez
Centro de Estudios de Informática
Universidad Central "Marta Abreu" de Las Villas
-----
"...hay locuras que son la locura
personales locuras de dos...
hay locuras sin nombre
sin fecha sin cura
que no vale la pena curar...
que una de ellas será mi morir."
Lic. Reinier Millo Sánchez
Centro de Estudios de Informática
Universidad Central "Marta Abreu" de Las Villas
Hello,
I have a problem building gcc-linaro-arm-linux-gnueabihf
toolchain for my x86_64 system. I download crosstool-ng (v1.13) and
toolchain source code (4.8-2014.03) from
http://releases.linaro.org/14.03/components/toolchain/binaries. I use
the example configuration linaro-arm-linux-gnueabihf (obtained from
ct-ng list-samples) and modify some entries using menuconfig option,
like the local tarballs directory (pointing to downloaded toolchains
source code directory) and the prefix directory (custom directory output).
This is the problem during the execution of "ct-ng build" command:
=================================================================
[INFO ] Installing final compiler
[EXTRA] Configuring final compiler
[EXTRA] Building final compiler
[EXTRA] AFMOYA: EMPIEZA A EJECUTARSE make jobsflags all
[EXTRA] -j5
[EXTRA] /home/afmoya/Descargas/build/.build/arm-linux-gnueabihf/build/build-cc
[ERROR] configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
[ERROR] make[2]: *** [configure-zlib] Error 1
[ERROR] make[1]: *** [all] Error 2
[ERROR]
[ERROR] >>
[ERROR] >> Error happened in: main[scripts/crosstool-NG.sh]
[ERROR] >>
[ERROR] >> For more info on this error, look at the file: 'build.log'
[ERROR] >> There is a list of known issues, some with workarounds, in:
[ERROR] >> '/opt/cross-linaro/share/doc/ct-ng-linaro-1.13.1-4.8-2014.03/B - Known issues.txt'
[ERROR]
[ERROR] Build failed in step 'Extracting and patching toolchain components'
[ERROR]
[ERROR] (elapsed: 11:18.57)
make: *** [build] Error 2
Highlighted in green some entries added for me in attemp to understand
the execution secuence.
The error is triggered in the "configure-zlib" target of
"${CT_TOP_DIR}/.build/arm-linux-gnueabihf/build/build-cc/Makefile". The
"configure.log" of the
"${CT_TOP_DIR}/.build/arm-linux-gnueabihf/build/build-cc/zlib/"
directory shows some errors (I don't know if the are significants):
LINE 83: Thread model: posix
LINE 84: gcc version 4.7.2 (Debian 4.7.2-5)
LINE 85: configure:3234: $? = 0
LINE 86: configure:3223: x86_64-build_unknown-linux-gnu-gcc -V >&5
LINE 87: gcc: error: unrecognized command line option '-V'
LINE 88: gcc: fatal error: no input files
LINE 89: compilation terminated.
LINE 90: configure:3234: $? = 4
LINE 91: configure:3223: x86_64-build_unknown-linux-gnu-gcc -qversion >&5
LINE 92: gcc: error: unrecognized command line option '-qversion'
LINE 93: gcc: fatal error: no input files
LINE 94: compilation terminated.
...
LINE 188: configure:6661: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
LINE 189: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
LINE 190: compilation terminated.
...
LINE 207: configure:6720: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
LINE 208: conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
LINE 209: compilation terminated.
...
LINE 318: configure:10852: x86_64-build_unknown-linux-gnu-gcc -E conftest.c
LINE 319: conftest.c:23:28: fatal error: ac_nonexistent.h: No such file or directory
LINE 320: compilation terminated.
Some idea of what's the problem?
This is my system info:
Linux afmoya-pc 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
and some tools version installed in my system:
gcc (Debian 4.7.2-5) 4.7.2
GNU Make 3.81
GNU Awk 4.0.1
...
Best regards:
Alexis Fajardo Moya.
== Progress ==
* Prototype scripting for macro-benchmarks for malloc (4/10, TCWG-441)
* glibc single thread optimization work (3/10, TCWG-436)
* Built releases of eglibc, gdb and binutils (2/10)
* glibc patch review and followup (1/10)
* Misc admin (expenses, LCU travel)
== Issues ==
* None
== Plan ==
* Various bits of patch followup
* More malloc macro-benchmark work
* See how single thread optimization discussion goes
* glibc benchmark graphing?
--
Will Newton
Toolchain Working Group, Linaro
== Progress ==
* Named Register (CARD-1246 2/10)
- Changing type of intrinsics, rebasing patch
* Build & Benchmark (CARD-716 6/10)
- Adding Clang+LLVM builds to CBuild2
- Re-setting APM's testing environment after replacement
* Background (2/10)
- Code review, etc.
- EuroLLVM 2014 outcome analysis, plans for 2015
== Plan ==
* Get Clang+LLVM in CBuild2
* Get Named registers in, then try Clang's parser
* Try SPEC on APM
hi,
For building arm64 kernel, I tried all toolchain released from
http://releases.linaro.org/latest/components/toolchain/binaries/
But it complained about some instructions bad:
/home/work/linux/arch/arm64/include/asm/irqflags.h: Assembler
messages:
/home/work/linux/arch/arm64/include/asm/irqflags.h:49: Error: no
such instruction: `msr daifset,'
/home/work/linux/arch/arm64/include/asm/irqflags.h:68: Error: no
such instruction: `mrs %rax,daif//arch_local_save_flags'
/home/work/linux/arch/arm64/include/asm/irqflags.h:49: Error: no
such instruction: `msr daifset,'
/home/work/linux/arch/arm64/include/asm/irqflags.h:68: Error: no
such instruction: `mrs %rax,daif//arch_local_save_flags'
/home/work/linux/arch/arm64/include/asm/irqflags.h:40: Error: no
such instruction: `msr daifclr,'
/home/work/linux/arch/arm64/include/asm/irqflags.h:68: Error: no
such instruction: `mrs %rax,daif//arch_local_save_flags'
/home/work/linux/arch/arm64/include/asm/irqflags.h:40: Error: no
such instruction: `msr daifclr,'
Could anyone tell how to solve it? thanks!
== Progress==
TCWG-435 needless busy-wait in lowlevellock.c (3/10)
* Patches ready, testing a bit slow & fiddly
TCWG-156 cortex-strings memset (3/10)
* Worried about noisy benchmarks
* Learned to use Lava
* Found some helpful internal docs
* Managed to tweak the code slightly
== Misc ==
Meetings/mail/etc 2/10
(Public) holiday 2/10
== Plan ==
Stop worrying and follow the general curve of the noisy benchmarks
(But also try to convince Maxim's spec scripts + lava to generate some
less noisy results)
Another public holiday next Monday
