On Mon, 1 Oct 2018 at 16:34, Arnd Bergmann arnd@arndb.de wrote:
On Mon, Oct 1, 2018 at 2:37 PM Christophe Lyon christophe.lyon@linaro.org wrote:
Hi Arnd,
After our discussion during Connect, I've uploaded to tarballs of binary toolchains for arm and aarch64: http://people.linaro.org/~christophe.lyon/toolchain-arm-none-linux-gnueabihf... http://people.linaro.org/~christophe.lyon/toolchain-aarch64-none-linux-gnu.t...
I've managed to build the Linux kernel with them except a problem with popcount on aarch64. I know Kugan worked on this, but I'm not sure about the current status.
I can update my scripts to upload these toolchains daily (after "Daily bump"), let me know if that suits you. They only support the C language, that's the stage1 compiler, I think it's OK for you.
These toolchains are built in the ST compute farm, on RHEL6 hosts, but it ran correctly on my Ubuntu-18 workstation.
Is that OK with you?
I gave the 32-bit toolchain a quick spin on my own box, it worked great here. I've discussed this with Kevin during Connect, he can probably knows more about how close we are to having multi-toolchain support ready to integrate this in kernelci.
I'm also adding the kernel-build-reports list to Cc here, so others can comment. For background: There was a request about including limited testing of daily gcc snapshots in kernelci, which would catch both regressions introduced in the compiler and newly added warnings about possible kernel bugs early. Christophe is already building arm and aarch64 compilers for his own toolchain testing every day and said he could upload those every day to a public location.
We probably don't want to add all combinations to the build farm, but doing arm and aarch64 builds on linux-next with the compiler of the day seems like a nice addition to me.
Christophe: I noticed that your arm compiler is over 50% slower than the gcc-8.1 release build I have. I assume this is mostly the result of your binary being a debug build rather than a release build that skips a lot of the checks. Does that sound right? Is this what you intended? I suppose using the debug build of the toolchain catches more bugs in the compiler itself, but it also adds some cost to the build servers.
Indeed, I configure GCC with --enable-checking, so as to catch more problems. In the past I missed regressions for lack of using this flag.
Arnd