> -----Original Message-----
> From: Gcc <gcc-boun...@gcc.gnu.org> On Behalf Of Jakub Jelinek via Gcc
> Sent: 30 April 2020 18:11
> To: gcc@gcc.gnu.org
> Subject: GCC 10.0.1 Status Report (2019-04-30)
>
> Status
> ======
>
> We have reached zero P1 regressions today and releases/gcc-10 branch has
> been created; GCC 10.1-rc1 will be built and announced later tonight
> or tomorrow.
> The branch is now frozen for blocking regressions and documentation
> fixes only, all changes to the branch require a RM approval now.
>
> If no show stoppers appear, we'd like to release 10.1 late next week,
> or soon after that, if any important issues are discovered and
> fixed, rc2 could be released next week.
Bootstrap and testing on aarch64-none-linux-gnu and arm-none-linux-gnueabihf
successful.
I've also built defconfig and allyesconfig kernels for both successfully.
I've tried -fanalyzer on an aarch64 (arm64) kernel and it gave some interesting
results although it did hit what I think is:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94689
I may commit https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545143.html to
fix the OOL atomics issue with glibc to the GCC 10 branch if possible once I
get a sanity check form Joseph and/or Florian.
Thanks,
Kyrill
>
>
> Quality Data
> ============
>
> Priority # Change from last report
> -------- --- -----------------------
> P1 0 - 21
> P2 208 - 14
> P3 14 - 1
> P4 173 - 5
> P5 21 - 2
> -------- --- -----------------------
> Total P1-P3 222 - 36
> Total 416 - 43
>
>
> Previous Report
> ===============
>
> https://gcc.gnu.org/pipermail/gcc/2020-April/000242.html
