On Mon, Oct 1, 2018 at 2:37 PM Christophe Lyon
<christophe.lyon(a)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-gnueabih…
> http://people.linaro.org/~christophe.lyon/toolchain-aarch64-none-linux-gnu.…
>
> 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.
Arnd
Here are the build results from automated periodic testing.
The tree being built was mainline, found at:
URL: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Branch: master
Topmost commits:
17b57b1883c12 Linux 4.19-rc6
9a10b063758c7 Merge tag 'auxdisplay-for-greg-v4.19-rc6' of https://github.com/ojeda/linux
9ba6873e16039 Merge tag 'libnvdimm-fixes2-4.19-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Build logs (stderr only) can be found at the following link (experimental):
http://arm-soc.lixom.net/buildlogs/mainline/v4.19-rc6/
Runtime: 44m 28s
Passed: 125
Failed: 0
Warnings: 13
Section mismatches: 0
-------------------------------------------------------------------------------
Failed defconfigs:
-------------------------------------------------------------------------------
No errors
Warnings:
arm64.allmodconfig:
include/linux/string.h:246:9: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=]
lib/ubsan.c:432:1: warning: ignoring attribute 'noreturn' in declaration of a built-in function '__ubsan_handle_builtin_unreachable' because it conflicts with attribute 'const' [-Wattributes]
include/linux/string.h:246:9: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=]
drivers/isdn/hardware/eicon/message.c:5985:1: warning: the frame size of 2096 bytes is larger than 2048 bytes [-Wframe-larger-than=]
arm.allmodconfig:
/tmp/ccvdm2rT.s:18124: Warning: using r15 results in unpredictable behaviour
/tmp/ccvdm2rT.s:18196: Warning: using r15 results in unpredictable behaviour
include/linux/string.h:246:9: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=]
lib/ubsan.c:432:1: warning: ignoring attribute 'noreturn' in declaration of a built-in function '__ubsan_handle_builtin_unreachable' because it conflicts with attribute 'const' [-Wattributes]
include/linux/string.h:246:9: warning: '__builtin_strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=]
arm.aspeed_g4_defconfig:
drivers/i2c/busses/i2c-aspeed.c:567:1: warning: label 'out' defined but not used [-Wunused-label]
arm.aspeed_g5_defconfig:
drivers/i2c/busses/i2c-aspeed.c:567:1: warning: label 'out' defined but not used [-Wunused-label]
arm.multi_v5_defconfig:
drivers/i2c/busses/i2c-aspeed.c:567:1: warning: label 'out' defined but not used [-Wunused-label]
arm.zx_defconfig:
kernel/debug/kdb/kdb_support.c:239:4: warning: 'strncpy' specified bound depends on the length of the source argument [-Wstringop-overflow=]
New syscalls:
arm io_pgetevents
No section mismatches