search for: wstringop

...been building R on Windows: In function 'R_chk_memset', inlined from 'do_aperm' at ../main/array.c:1754:5: ../main/memory.c:3578:16: warning: 'memset' specified bound between 18446744056529682432 and 18446744073709551608 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] 3578 | return n ? memset(s, c, n) : s; | No idea if it is related but I thought I should mention it. Thank you, Avi

...t std::vector<double>&)? at ../src/literanger/utility_math.h:99:48: /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ?void* __builtin_memmove(void*, const void*, long unsigned int)? writing between 9 and 9223372036854775807 bytes into a region of size 8 overflows the destination [-Wstringop-overflow=] 437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num);

...ficant" warning: * checking whether package ?QCA? can be installed ... [35s/35s] WARNING Found the following significant warnings: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ?__builtin_strncpy? output may be truncated copying 12 bytes from a string of length 79 [-Wstringop-truncation] See ?/srv/hornik/tmp/CRAN/QCA.Rcheck/00install.out? for details. I know the cause of this: using a cursomized version of some external C library, coupled with <SystemRequirements: GNU make> in the Description. But I do not know hot to get past this warning, since it refers to a...

...ble>&)? at ../src/literanger/utility_math.h:99:48: > /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ?void* > __builtin_memmove(void*, const void*, long unsigned int)? writing > between 9 and 9223372036854775807 bytes into a region of size 8 > overflows the destination [-Wstringop-overflow=] > 437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num); The same problem (different reproducer, slightly different warning, but same place in the standard library and similar circumstances) has been reported as a false positive in GCC, Bug 109717: https://gcc.gnu.org...

..., -Wpacked-not-aligned) subdir-ccflags-y += $(call cc-option, -Wformat-overflow) -# FIXME: fix -Wformat-truncation warnings and uncomment -#subdir-ccflags-y += $(call cc-option, -Wformat-truncation) +subdir-ccflags-y += $(call cc-option, -Wformat-truncation) subdir-ccflags-y += $(call cc-option, -Wstringop-truncation) # The following turn off the warnings enabled by -Wextra ifeq ($(findstring 2, $(KBUILD_EXTRA_WARN)),) -- 2.39.2

.../src/literanger/utility_math.h:99:48: > > /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ?void* > > __builtin_memmove(void*, const void*, long unsigned int)? writing > > between 9 and 9223372036854775807 bytes into a region of size 8 > > overflows the destination [-Wstringop-overflow=] > > 437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num); > > The same problem (different reproducer, slightly different warning, but > same place in the standard library and similar circumstances) has been > reported as a false positive in GCC, Bug 109...

...gt; subdir-ccflags-y += $(call cc-option, -Wformat-overflow) > -# FIXME: fix -Wformat-truncation warnings and uncomment > -#subdir-ccflags-y += $(call cc-option, -Wformat-truncation) > +subdir-ccflags-y += $(call cc-option, -Wformat-truncation) > subdir-ccflags-y += $(call cc-option, -Wstringop-truncation) > # The following turn off the warnings enabled by -Wextra > ifeq ($(findstring 2, $(KBUILD_EXTRA_WARN)),) > -- > 2.39.2

I'm not sure if this is a GCC bug or a bug in our code, but the attached workaround fixes it for me. Rich.

...mset', >>> inlined from 'do_aperm' at ../main/array.c:1754:5: >>> ../main/memory.c:3578:16: warning: 'memset' specified bound between >>> 18446744056529682432 and 18446744073709551608 exceeds maximum object >>> size 9223372036854775807 [-Wstringop-overflow=] >>> 3578 | return n ? memset(s, c, n) : s; >>> | >>> >>> No idea if it is related but I thought I should mention it. >>> Thank you, >>> >>> Avi >>> >>> ________________________________________...

...nt-cast -Wpragmas -Wpsabi -Wrestrict -Wreturn-local-addr -Wreturn-type -Wscalar-storage-order -Wsequence-point -Wshadow -Wshift-count-negative -Wshift-count-overflow -Wshift-negative-value -Wsizeof-array-argument -Wsizeof-pointer-div -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-prototypes -Wstringop-truncation -Wsuggest-attribute=cold -Wsuggest-attribute=const -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wsuggest-final-methods -Wsuggest-final-types -Wswitch -Wswitch-bool -Wswitch-unreachable -Wsync-nand -Wtautological-compare -Wtrampolines -Wtrigraphs -Wtyp...

...ble>&)? at ../src/literanger/utility_math.h:99:48: > /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ?void* > __builtin_memmove(void*, const void*, long unsigned int)? writing > between 9 and 9223372036854775807 bytes into a region of size 8 > overflows the destination [-Wstringop-overflow=] > 437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num); Perhaps you could try creating a minimal reproducible example, standalone C++ program, which still reproduces the warning, and report to GCC (or libstdc++). You may get a response it is a duplicate of...

Both Coverity and GCC with -Wstringop-overflow noticed that nvif_outp_acquire_dp() accidentally defined its second argument with 1 additional element: drivers/gpu/drm/nouveau/dispnv50/disp.c: In function 'nv50_pior_atomic_enable': drivers/gpu/drm/nouveau/dispnv50/disp.c:1813:17: error: 'nvif_outp_acquire_dp' accessing...

...hed it already or if you want me to push it to drm- misc On Wed, 2023-01-25 at 12:15 -0800, Kees Cook wrote: > Ping. I'll take this via my tree unless someone else wants to take it... > > On Sun, Nov 27, 2022 at 10:30:41AM -0800, Kees Cook wrote: > > Both Coverity and GCC with -Wstringop-overflow noticed that > > nvif_outp_acquire_dp() accidentally defined its second argument with 1 > > additional element: > > > > drivers/gpu/drm/nouveau/dispnv50/disp.c: In function 'nv50_pior_atomic_enable': > > drivers/gpu/drm/nouveau/dispnv50/disp.c:1813:17...

On Thu, Sep 24, 2020 at 2:58 PM Ján Tomko <jtomko@redhat.com> wrote: > On a Thursday in 2020, Wei Wang wrote: > >Seems it didn't appear on the mailing list, resent it. > > > > Hi folks, > > > >I'm trying to build libvirt using meson with the latest upstream libvirt, > >but the compilation fails: > >(followed on

From: Xiongfeng Wang <xiongfeng.wang at linaro.org> gcc-8 reports drivers/gpu/drm/nouveau/nvif/client.c: In function 'nvif_client_init': ./include/linux/string.h:245:9: warning: '__builtin_strncpy' specified bound 32 equals destination size [-Wstringop-truncation] We need to use strlcpy() to make sure the dest string is nul-terminated. Signed-off-by: Xiongfeng Wang <xiongfeng.wang at linaro.org> --- drivers/gpu/drm/nouveau/nvif/client.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvif/clien...

...n (str, SIZE_MAX); } ---------------------------------------------------------------------- $ gcc -O2 -Wall -c test.c In function ‘copyn’, inlined from ‘copy’ at test.c:15:10: test.c:9:10: warning: ‘strndup’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] 9 | return strndup (str, n); | ^~~~~~~~~~~~~~~~ $ gcc --version gcc (GCC) 10.2.1 20200826 (Red Hat 10.2.1-3) Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTA...

...g: > > * checking whether package ?QCA? can be installed ... [35s/35s] WARNING > Found the following significant warnings: > /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ?__builtin_strncpy? output may be truncated copying 12 bytes from a string of length 79 [-Wstringop-truncation] > See ?/srv/hornik/tmp/CRAN/QCA.Rcheck/00install.out? for details. > > > I know the cause of this: using a cursomized version of some external C library, coupled with <SystemRequirements: GNU make> in the Description. > > But I do not know hot to get past this...

...string.h:535, from kex.c:34: In function 'explicit_bzero', inlined from 'kex_free_newkeys' at kex.c:743:2: /usr/include/bits/string_fortified.h:72:3: warning: '__explicit_bzero_chk' writing 48 bytes into a region of size 8 overflows the destination [-Wstringop-overflow=] 72 | __explicit_bzero_chk (__dest, __len, __glibc_objsize0 (__dest)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from kex.c:53: kex.h: In function 'kex_free_newkeys': kex.h:116:18: note: destination object 'name' of s...

...h Hughes (2): conntrackd: search for RPC headers conntrackd: Use strdup in lexer Brian Haley (1): conntrack: Allow protocol number zero Jan-Martin Raemer (1): conntrackd: UDP IPv6 destination address not usable (Bug 1378) Jose M. Guisado Gomez (1): src: fix strncpy -Wstringop-truncation warnings Michal Kubecek (2): conntrackd: use correct max unix path length conntrackd: cthelper: Add new SLP helper Pablo Neira Ayuso (8): build: use -Wno-sign-compare with autogenerated flex code conntrack: extend nfct_mnl_socket_open() to use it to handle event...

...------------------------------------------------------------------ > > $ gcc -O2 -Wall -c test.c > In function ‘copyn’, > inlined from ‘copy’ at test.c:15:10: > test.c:9:10: warning: ‘strndup’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=] > 9 | return strndup (str, n); > | ^~~~~~~~~~~~~~~~ > > $ gcc --version > gcc (GCC) 10.2.1 20200826 (Red Hat 10.2.1-3) > Copyright (C) 2020 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is...