Re: Automated report: NetBSD-current/i386 build failure

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Sun, 16 Jun 2024 at 20:23, matthew green <mrg%eterna23.net@localhost> wrote:
>
> OK, this should be fixed now at bsd.own.mk 1.1378.
>
> the problem was that for the xen kernel builds, MACHINE=xen,
> and the bsd.own.mk snippet was checking for "i386" and "amd64",
> and not "xen".  i was able to trigger the failure in a tree
> using an empty mk.conf, still not sure why i didn't see it in
> my normal trees.
>
>
> .mrg.


I am at present getting:
.....
#   compile  INSTALL_XEN3_DOMU/aes_ni.o
/dumps/sysbuild/amd64/tools/bin/x86_64--netbsd-gcc
-Wno-stringop-overflow -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse
-mno-avx -msoft-float -mno-fp-ret-in-387 -ffreestanding -f
no-zero-initialized-in-bss -fno-delete-null-pointer-checks -g -O2
-fno-omit-frame-pointer -fstack-protector -Wstack-protector --param
ssp-buffer-size=1 -fstack-usage -Wstack-usage=
3584 -fno-strict-aliasing -fno-common -Wno-stringop-overflow
-std=gnu99 -Werror -Wall -Wno-main -Wno-format-zero-length
-Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes -Wo
ld-style-definition -Wswitch -Wshadow -Wcast-qual -Wwrite-strings
-Wno-unreachable-code -Wno-pointer-sign -Wno-attributes
-Wno-type-limits -Wextra -Wno-unused-parameter -Wold-style
-definition -Wno-sign-compare -Wno-address-of-packed-member -Walloca
--sysroot=/dumps/sysbuild/amd64/destdir -Damd64 -Dx86_64 -I.
-I/dumps/sysbuild/amd64/obj/home/sysbuild/src/sys/
arch/amd64/compile/INSTALL_XEN3_DOMU/xen-ma
-I/home/sysbuild/src/sys/external/mit/xen-include-public/dist/
-I/home/sysbuild/src/sys/external/bsd/libnv/dist
-I/home/sysbuild/src/sys
/external/bsd/acpica/dist
-I/home/sysbuild/src/sys/../common/lib/libx86emu
-I/home/sysbuild/src/sys/../common/lib/libc/misc
-I/home/sysbuild/src/sys/../common/include -I/home/sysbu
ild/src/sys/arch -I/home/sysbuild/src/sys -nostdinc -DCOMPAT_UTILS
-D__XEN_INTERFACE_VERSION__=0x3020a -DDIAGNOSTIC -DCOMPAT_44 -D_KERNEL
-D_KERNEL_OPT -std=gnu99 -I/home/sysbuild/
src/sys/lib/libkern/../../../common/lib/libc/quad
-I/home/sysbuild/src/sys/lib/libkern/../../../common/lib/libc/string
-I/home/sysbuild/src/sys/lib/libkern/../../../common/lib/libc
/arch/x86_64/string
-I/home/sysbuild/src/sys/lib/libkern/../../../common/lib/libc/arch/x86_64/atomic
-I/home/sysbuild/src/sys/lib/libkern/../../../common/lib/libc/hash/sha3
-D_FORT
IFY_SOURCE=2 -I/home/sysbuild/src/sys/external/bsd/libnv/dist -c
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c -o aes_ni.o
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c: In function
'aesni_xts_dec_impl':
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c:202:17: error:
'aesni_xts_dec8' reading 128 bytes from a region of size 16
[-Werror=stringop-overread]
  202 |                 aesni_xts_dec8(dec, in, out, nbytes, iv, nrounds);
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c:202:17: note:
referencing argument 2 of type 'const uint8_t[128]' {aka 'const
unsigned char[128]'}
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c:202:17: note:
referencing argument 3 of type 'uint8_t[128]' {aka 'unsigned
char[128]'}
/home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c:202:17: note:
referencing argument 5 of type 'uint8_t[16]' {aka 'unsigned char[16]'}
In file included from /home/sysbuild/src/sys/crypto/aes/arch/x86/aes_ni.c:46:
---

and it repeats another 4.5 times, showing different number of bytes
being read, before quitting.

Chavdar

----