search for: stringops

Hello, For the very first time, I tried the command bellow on a newly build Debian Buster box on which I successfully built Asterisk 17.2.0 before. I got : # contrib/scripts/install_prereq install-unpackaged *** Installing NBS (Network Broadcast Sound) *** A nbs-trunk/LICENSE A nbs-trunk/nbsclient.c A nbs-trunk/nbsd.c A nbs-trunk/nbs.h A nbs-trunk/nbscat.c A nbs-trunk/Makefile

hello when i Tried to compile xf86-video-nouveau come this message: cc1: error: unrecognized command line option "-minline-all-stringops" make[2]: *** [nv_accel_common.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

...ectory `/home/tavvva/Install/nouveau/xf86-video-nouveau/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/drm -I/usr/include/X11/dri -I/usr/include/drm -I/usr/include/nouveau -g -O2 -Wall -minline-all-stringops -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/drm -I/usr/include/X11/dri -MT nouveau_exa.lo -MD -MP -MF .deps/nouveau_exa.Tpo -c -o nouveau_exa.lo nouveau_exa.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/drm -I/usr/inclu...

On 9/3/20 4:41 AM, Richard W.M. Jones wrote: > Previously with GCC 10.2 this code produced: > > In function ‘nbdkit_strndup_intern’, > inlined from ‘nbdkit_strdup_intern’ at public.c:839:10: > public.c:827:10: error: ‘strndup’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Werror=stringop-overflow=] > 827 | copy = strndup (str,

I'm trying to build nouveau form git. The compile fails with: gcc -DHAVE_CONFIG_H -I. -I.. -D_XOPEN_SOURCE=500 -I -I/usr/include/pixman-1 -I/usr/include/drm -I/usr/include/X11/dri -g -O2 -Wall -minline-all-stringops -D_XOPEN_SOURCE=500 -I -I/usr/include/pixman-1 -I/usr/include/drm -I/usr/include/X11/dri -MT nouveau_device.lo -MD -MP -MF .deps/nouveau_device.Tpo -c nouveau_device.c -fPIC -DPIC -o .libs/nouveau_device.o In file included from nouveau_device.c:27: nouveau_drmif.h:47: error: expected ?=?, ?,?, ?;?,...

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.

Hello David, thanks for detailed response! Do you have any tests that you use to measure the PGO effectiveness? I have tested clang version 6.0 with the same sample that Jie Chen used in 2016 and actually both frontend-based PGO and IR-based make code run slower, see the average time: clang++ -O3: 3.15 sec  clang++ -O3 and -fprofile-instr-use: 3.160 sec clang++ -O3 and -fprofile-use: 3.180 sec

On Sun, Feb 4, 2018 at 9:59 PM, Victor Leschuk <vleschuk at accesssoftek.com> wrote: > Hello David! > > I have recently started acquaintance with PGO in LLVM/clang and found > your e-mail thread: > http://lists.llvm.org/pipermail/llvm-dev/2016-May/099395.html . Here you > posted a nice list of optimizations that use profiling and of those > which could be using but

gcc 8 gripes (when using './configure --enable-gcc-warnings'): nbd.c: In function 'nbd_open': nbd.c:470:3: error: 'strncpy' specified bound 108 equals destination size [-Werror=stringop-truncation] strncpy (sock.sun_path, sockname, sizeof (sock.sun_path)); The warning is a false positive, given that we currently reject names >= sizeof(sock.sun_path), and thus we are

Hello David! I have recently started acquaintance with PGO in LLVM/clang and found your e-mail thread: http://lists.llvm.org/pipermail/llvm-dev/2016-May/099395.html . Here you posted a nice list of optimizations that use profiling and of those which could be using but don't. However that thread is about 2 years old. Could you please kindly let me know if there were any significant changes in

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 16 bytes in a region of size 15 [-Werror=stringop-overflow=]

David, could you please clarify on which code did you gain 10% improvement? I have run numerous tests with and w/o this option and it looks like it has no effect on performance (I am talking of the old 2016 sample to be concrete). Maybe we could investigate it together? Just tell me where to start? On 02/07/2018 02:11 AM, Xinliang David Li wrote: > Victor, thanks for the experiment. > >

Victor, thanks for the experiment. My suspicion is it is due to the remaining issues with block layout -- especially with loop rotation (with PGO). Another problem is that tail dup is not happening after loop rotation which can limit the effectiveness of loop rotation. I tried the internal option -mllvm -force-precise-rotation-cost and there is about 10% speedup with -fprofile-use. This option

Sorry! I've been pretty busy until now, this is: Reviewed-by: Lyude Paul <lyude at redhat.com> Let me know if you've pushed 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:

Victor, please file a bug tracking the issue. We can put relevant information there including test cases used in the experiment etc. thanks, David On Wed, Feb 7, 2018 at 2:15 PM, Victor Leschuk <vleschuk at accesssoftek.com> wrote: > David, could you please clarify on which code did you gain 10% > improvement? I have run numerous tests with and w/o this option and it > looks

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

Previously with GCC 10.2 this code produced: In function ‘nbdkit_strndup_intern’, inlined from ‘nbdkit_strdup_intern’ at public.c:839:10: public.c:827:10: error: ‘strndup’ specified bound 18446744073709551615 exceeds maximum object size 9223372036854775807 [-Werror=stringop-overflow=] 827 | copy = strndup (str, n); | ^~~~~~~~~~~~~~~~ --- server/public.c | 16

Hi folks, I have several build environments in which I must build rsync, and in some, but not all of them, the build fails when built with -Wall -Werror due to this warning: In file included from /usr/include/string.h:495, from /home/demartin/BuildClients/cobrasync-8.80-alsi11-lib32/cobrasync/rsync-3.2.7/rsync.h:339, from

I have decided to make SYSLINUX 2.10-pre6 a release candidate. Please test it out if you can; if it works OK I will release it as 2.10 some time in the middle of the week. Thanks! -hpa

...#39;s a patch I used. --- memdisk/Makefile.orig 2004-01-24 16:37:22.000000000 -0500 +++ memdisk/Makefile 2004-08-18 06:34:53.000000000 -0400 @@ -17,11 +17,12 @@ then echo $(1); else echo $(2); fi) M32 := $(call gcc_ok,-m32,) +MINLINE := $(call gcc_ok,-minline-all-stringops,) ALIGN := $(call gcc_ok,-falign-functions=0 -falign-jumps=0 -falign-loops=0,-malign-functions=0 -malign-jumps=0 -malign-loops=0) CC = gcc $(M32) CFLAGS = -g -W -Wall -Os -fomit-frame-pointer -march=i386 $(ALIGN) \ - -DVERSION='"$(VERSION)"' -DDATE='&qu...