On Wed, 6 Nov 2019, Jeff Law wrote: > > It is what I believe has also broken glibc: > > > > In file included from ../sysdeps/riscv/libc-tls.c:19: > > ../csu/libc-tls.c: In function '__libc_setup_tls': > > ../csu/libc-tls.c:209:30: error: array subscript 1 is outside the bounds of > > an interior zero-length array 'struct dtv_slotinfo[0]' > > [-Werror=zero-length-bounds] > > 209 | static_slotinfo.si.slotinfo[1].map = main_map; > > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~ > > In file included from ../sysdeps/riscv/ldsodefs.h:46, > > from ../sysdeps/gnu/ldsodefs.h:46, > > from ../sysdeps/unix/sysv/linux/ldsodefs.h:25, > > from ../sysdeps/unix/sysv/linux/riscv/ldsodefs.h:22, > > from ../csu/libc-tls.c:21, > > from ../sysdeps/riscv/libc-tls.c:19: > > ../sysdeps/generic/ldsodefs.h:423:7: note: while referencing 'slotinfo' > > 423 | } slotinfo[0]; > > | ^~~~~~~~ > > cc1: all warnings being treated as errors > > > > (here in a RISC-V build). > > > > Has anybody looked yet into how the breakage could possibly be addressed? > Yea, Florian posted patches over the weekend to fix glibc. They're > still going through the review/update cycle.
Thanks, I have found them now, now that I knew what to look for and in what time frame. Unfortunately there's no mention of the error message or at least the name of the `-Wzero-length-bounds' option (which is how I found the GCC patch) in the respective glibc change descriptions so my mailing list searches returned nothing. I think it would be good to try and have keywords potentially looked for in change descriptions, and verbatim error messages are certainly good candidates IMO. So I went for `-Wno-zero-length-bounds' for my glibc build for the time being, as my objective now is to get some outstanding GCC stuff in before stage 1 ends rather than being drawn into glibc build issues. Maciej
