search for: __builtin_strncpy

...[...] app_voicemail.c:460: warning: assignment makes pointer from integer without a cast app_voicemail.c:461: warning: implicit declaration of function `PQgetisnull' app_voicemail.c:462: warning: implicit declaration of function `PQgetvalue' app_voicemail.c:462: warning: passing arg 2 of `__builtin_strncpy' makes pointer from integer without a cast app_voicemail.c:464: warning: passing arg 2 of `__builtin_strncpy' makes pointer from integer without a cast app_voicemail.c:466: warning: passing arg 2 of `__builtin_strncpy' makes pointer from integer without a cast app_voicemail.c:468: warni...

...passes ok on all platforms but Debian, where CRAN responds with an automatic "significant" 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 D...

...nal function: sbyte * (sbyte *, sbyte *, uint) * strncpy" Strncpy is used as part of my compiler's run-time library, and it was compiled with the C-frontend for LLVM. Looking at the assembly, the function is declared at the top of the file; declare sbyte* %strncpy(sbyte*,sbyte*,uint) ;; __builtin_strncpy And it is called like this: %tmp.12 = call sbyte* (sbyte*, sbyte*, uint)* %strncpy(sbyte* %tmp.15, sbyte* %tmp.23, uint %tmp.27) What am I forgetting to do? What is the right way to link to the string functions? Thanks, -Eric Zimmerman

...ns.cpp) or use the C backend. -Chris > Strncpy is used as part of my compiler's run-time library, and it was > compiled with the C-frontend for LLVM. Looking at the assembly, the > function is declared at the top of the file; > > declare sbyte* %strncpy(sbyte*,sbyte*,uint) ;; __builtin_strncpy > > And it is called like this: > %tmp.12 = call sbyte* (sbyte*, sbyte*, uint)* %strncpy(sbyte* > %tmp.15, sbyte* %tmp.23, uint %tmp.27) > > What am I forgetting to do? What is the right way to link to the > string functions? Thanks, > > -Eric Zimmerman >

...is > > > > Strncpy is used as part of my compiler's run-time library, and it was > > compiled with the C-frontend for LLVM. Looking at the assembly, the > > function is declared at the top of the file; > > > > declare sbyte* %strncpy(sbyte*,sbyte*,uint) ;; __builtin_strncpy > > > > And it is called like this: > > %tmp.12 = call sbyte* (sbyte*, sbyte*, uint)* %strncpy(sbyte* > > %tmp.15, sbyte* %tmp.23, uint %tmp.27) > > > > What am I forgetting to do? What is the right way to link to the > > string functions? Thanks, > &...

...In function get_answer: bcmxcp_usb.c:47: warning: pointer targets in passing argument 3 of usb_interrupt_read differ in signedness gcc -I../include -O -Wall -Wsign-compare -c tripplite_usb.c tripplite_usb.c: In function hex2d: tripplite_usb.c:350: warning: pointer targets in passing argument 1 of __builtin_strncpy differ in signedness tripplite_usb.c:350: warning: pointer targets in passing argument 2 of __builtin_strncpy differ in signedness tripplite_usb.c:352: warning: pointer targets in passing argument 1 of strtol differ in signedness tripplite_usb.c: In function hexascdump: tripplite_usb.c:370: warning...

gcc-8 reports drivers/gpu/drm/nouveau/nvkm/engine/pm/base.c: In function 'nvkm_perfmon_mthd': include/linux/string.h:265:9: error: '__builtin_strncpy' specified bound 64 equals destination size [-Werror=stringop-truncation] We need one less byte or call strlcpy() to make it a nul-terminated string. Signed-off-by: Arnd Bergmann <arnd at arndb.de> --- drivers/gpu/drm/nouveau/nvkm/engine/pm/base.c | 6 +++--- 1 file changed, 3 insertio...

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...

...latforms but Debian, where CRAN responds with an automatic "significant" 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: G...

...s' app_rxfax.c:78: warning: implicit declaration of function 'fax_get_far_ident' app_rxfax.c:79: warning: implicit declaration of function 'fax_get_local_ident' app_rxfax.c: In function 'rxfax_exec': app_rxfax.c:189: warning: pointer targets in passing argument 1 of '__builtin_strncpy' differ in signedness app_rxfax.c:259: warning: passing argument 1 of 'fax_init' from incompatible pointer type app_rxfax.c:260: error: 't30_state_t' has no member named 'verbose' app_rxfax.c:263: warning: implicit declaration of function 'fax_set_local_ident' ap...

...ian, where CRAN responds with an automatic "significant" 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 <SystemR...

...> Strncpy is used as part of my compiler's run-time library, and it was > > > compiled with the C-frontend for LLVM. Looking at the assembly, the > > > function is declared at the top of the file; > > > > > > declare sbyte* %strncpy(sbyte*,sbyte*,uint) ;; __builtin_strncpy > > > > > > And it is called like this: > > > %tmp.12 = call sbyte* (sbyte*, sbyte*, uint)* %strncpy(sbyte* > > > %tmp.15, sbyte* %tmp.23, uint %tmp.27) > > > > > > What am I forgetting to do? What is the right way to link to the > > &gt...

...Chris > > > >>Strncpy is used as part of my compiler's run-time library, and it was >>compiled with the C-frontend for LLVM. Looking at the assembly, the >>function is declared at the top of the file; >> >>declare sbyte* %strncpy(sbyte*,sbyte*,uint) ;; __builtin_strncpy >> >>And it is called like this: >> %tmp.12 = call sbyte* (sbyte*, sbyte*, uint)* %strncpy(sbyte* >>%tmp.15, sbyte* %tmp.23, uint %tmp.27) >> >>What am I forgetting to do? What is the right way to link to the >>string functions? Thanks, >> >>-...