RFC Update CI to using GCC 11.0 / LLVM-11
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest7 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | ARM: mvebu: a38x: Correct mismatched bound warningsdrivers/ | +7 | 4 replies | |
| 2/7 | freescale: Drop unnecessary cpld_data_t non-typedefboard/ board/ board/ | +3 | 1 reply | |
| 3/7 | eb_cpu5282: Declare diplay_width / display_height as externsboard/ | +2 | 1 reply | |
| 4/7 | pinctrl: mscc: Fix multiple definition errordrivers/ | +2 | 3 replies | |
| 5/7 | Makefile: Disable gcc-10.0 warningsMakefile | +4 | 1 reply | |
| 6/7 | bootstage: Eliminate when not enabledarch/ board/ board/ +7 more | +20 | 1 reply | |
| 7/7 | TEST: Move to gcc-11.0 prerelease and LLVM-11.azure-pipelines.yml .gitlab-ci.yml tools/ | +32 | 9 replies |
Reviews trailers per patch
1 of 7 patches has a Reviewed-by or Acked-by.
| Patch | Horatiu Vultur | Daniel Schwierzeck |
|---|---|---|
| 1/7 | ||
| 2/7 | ||
| 3/7 | ||
| 4/7 | R-b | R-b |
| 5/7 | ||
| 6/7 | ||
| 7/7 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC 0/7] Update CI to using GCC 11.0 / LLVM-11
Hey all,
This series does most of the work required to move to using GCC-11.0 to build in CI. The first thing is I realized I forgot to update buildman to know to where to fetch gcc-11 from, but I'll take care of that later. Next, this ends up using the last gcc-11 snapshot as the gcc-11.0 prebuilds aren't quite up on kernel.org, but will be soon.
The real issues here and I'd like some feedback on, and need some help with are:
- grub + riscv32 + gcc-11 doesn't build, and this seems known but not addressed yet. I don't know what we want to do here as it's for running some tests.
- I cannot get x86 to build. With this series the failures are:
https://source.denx.de/u-boot/u-boot/-/jobs/263745
But I can't find a good way to address that multiple definition error of _X86EMU_env that doesn't break some other platform. At heart, Chromebooks enable the emulation and we have both chromebook_link and chromebook_link64 as builds, so we have both X86_64 and !X86_64 builds. I don't know the best way to deal with this, but I also wonder if the bios_emulation code doesn't need a rather large cleaning perhaps?
Signature · 1 line
Tom