On Thu, 7 Nov 2024 23:02:22 +0100 Bastian Germann <b...@debian.org> wrote:
On Wed, 6 Nov 2024 14:39:19 +0200 Adrian Bunk <b...@debian.org> wrote:
> > Upstream might be qualified to determine whether this is an mbedtls or gcc
bug.
> >
> > The easiest short-term workaround to unblock the transition is
> > export DEB_CFLAGS_MAINT_APPEND = -Wno-error=array-bounds
>
> This suggestion from my original bug report worked for me when I tested
> it back then.
Works for me.
the patch is creating a patch file, not a real patch
diff -pruN 3.6.2-1/debian/patches/100-fix-gcc14-build.patch
3.6.2-1ubuntu4/debian/patches/100-fix-gcc14-build.patch
--- 3.6.2-1/debian/patches/100-fix-gcc14-build.patch 1970-01-01
00:00:00.000000000 +0000
+++ 3.6.2-1ubuntu4/debian/patches/100-fix-gcc14-build.patch 2024-10-30
19:01:48.000000000 +0000
@@ -0,0 +1,11 @@
+--- a/library/common.h
++++ b/library/common.h
+@@ -199,7 +199,7 @@ static inline void mbedtls_xor(unsigned
+ uint8x16_t x = veorq_u8(v1, v2);
+ vst1q_u8(r + i, x);
+ }
+-#if defined(__IAR_SYSTEMS_ICC__)
++#if defined(__IAR_SYSTEMS_ICC__) || (defined(MBEDTLS_COMPILER_IS_GCC) &&
MBEDTLS_GCC_VERSION >= 140100)
+ /* This if statement helps some compilers (e.g., IAR) optimise out the
byte-by-byte tail case
+ * where n is a constant multiple of 16.
+ * For other compilers (e.g. recent gcc and clang) it makes no difference
if n is a compile-time
this one works
G.
