Re: Compile warning in insexpand.c with +eval after applying patches 9.1.189-190

2024-03-21 Fir de Conversatie Christian Brabandt
On Mi, 20 Mär 2024, Tony Mechelynck wrote: > For instance in Normal build : > > In function ‘get_complete_info’, > inlined from ‘f_complete_info’ at insexpand.c:3175:5: > insexpand.c:3123:31: warning: ‘li’ may be used uninitialized > [-Wmaybe-uninitialized] > 3123 |

Compile warning in insexpand.c with +eval after applying patches 9.1.189-190

2024-03-20 Fir de Conversatie Tony Mechelynck
For instance in Normal build : In function ‘get_complete_info’, inlined from ‘f_complete_info’ at insexpand.c:3175:5: insexpand.c:3123:31: warning: ‘li’ may be used uninitialized [-Wmaybe-uninitialized] 3123 | ret = list_append_dict(li, di); |

Re: Compile warning -Wmaybe-uninitialized about xxd (in gcc 13.2.1) for all featuresets of Vim

2023-10-08 Fir de Conversatie Christian Brabandt
On Fr, 06 Okt 2023, Tony Mechelynck wrote: > cd xxd; CC="gcc" CFLAGS=" -O2 -fno-strength-reduce -Wall > -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE > -D_FORTIFY_SOURCE=1" LDFLAGS="-L/usr/local/lib -Wl,--as-needed" \ > make -f Makefile > make[1]: Entering directory '/root/

Compile warning -Wmaybe-uninitialized about xxd (in gcc 13.2.1) for all featuresets of Vim

2023-10-06 Fir de Conversatie Tony Mechelynck
cd xxd; CC="gcc" CFLAGS=" -O2 -fno-strength-reduce -Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1" LDFLAGS="-L/usr/local/lib -Wl,--as-needed" \ make -f Makefile make[1]: Entering directory '/root/.build/vim/vim-hg/src/shadow-tiny/xxd' gcc -O2 -fno-str

patch 9.0.1699: compile warning for xdiff/xutils on MS-Windows

2023-08-12 Fir de Conversatie Christian Brabandt
patch 9.0.1699: compile warning for xdiff/xutils on MS-Windows Commit: https://github.com/vim/vim/commit/6c313bbb043745a60a7ee30a78edb907260b764a Author: Mike Williams Date: Sat Aug 12 20:47:43 2023 +0200 patch 9.0.1699: compile warning for xdiff/xutils on MS-Windows Problem

Re: Compile warning on ucrt build of mingw

2022-04-17 Fir de Conversatie John Marriott
On 17-Apr-2022 19:58, Bram Moolenaar wrote: John Marriott wrote: I recently started using a ucrt enabled build of mingw64 (gcc 11.2.0) which gives me this compile warning: gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H

Re: Compile warning on ucrt build of mingw

2022-04-17 Fir de Conversatie Bram Moolenaar
John Marriott wrote: > I recently started using a ucrt enabled build of mingw64 (gcc 11.2.0) > which gives me this compile warning: > > gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 > -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -D__USE_MINGW_ANSI_STDIO

Compile warning on ucrt build of mingw

2022-04-16 Fir de Conversatie John Marriott
I recently started using a ucrt enabled build of mingw64 (gcc 11.2.0) which gives me this compile warning: gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -D__USE_MINGW_ANSI_STDIO -pipe -march=native -Wall -O3 -fomit-frame-pointer

Re: After applying patches 8.2 84 and 85: Link error in Tiny and Small (undefind reference to clear_tv in insexpand.o), compile warning (unused variable s in dict.c) in other builds

2020-01-04 Fir de Conversatie Bram Moolenaar
Tony wrote: > In Tiny and Small: > > link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly. > gcc -L/usr/local/lib -Wl,--as-needed-o vi objects/arabic.o > objects/arglist.o objects/autocmd.o objects/beval.o objects/buffer.o > objects/change.o objects/blob.o objects/blowfis

After applying patches 8.2 84 and 85: Link error in Tiny and Small (undefind reference to clear_tv in insexpand.o), compile warning (unused variable s in dict.c) in other builds

2020-01-04 Fir de Conversatie Tony Mechelynck
In Tiny and Small: link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly. gcc -L/usr/local/lib -Wl,--as-needed-o vi objects/arabic.o objects/arglist.o objects/autocmd.o objects/beval.o objects/buffer.o objects/change.o objects/blob.o objects/blowfish.o objects/cindent.o objec

Re: Compile warning in Tiny but not in Huge in os_unix.c after applying patches 1609-1612

2018-03-17 Fir de Conversatie Bram Moolenaar
Tony wrote: > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/os_unix.o > os_unix.c > os_unix.c: In function ‘mch_call_shell_fork’: > os_unix.c:4591:13: warning: unused variable ‘p’ [-Wunused-variable] > char_u *

Compile warning in Tiny but not in Huge in os_unix.c after applying patches 1609-1612

2018-03-16 Fir de Conversatie Tony Mechelynck
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1-o objects/os_unix.o os_unix.c os_unix.c: In function ‘mch_call_shell_fork’: os_unix.c:4591:13: warning: unused variable ‘p’ [-Wunused-variable] char_u *p; ^ Best

Re: Compile warning -Wmaybe-uninitialized in terminal.c at or maybe before 8.0.798

2017-07-29 Fir de Conversatie Bram Moolenaar
Tony Mechelynck wrote: > gvim with GTK3 GUI was so untractable recently on my new openSUSE 42.3 > system that I decided to "downgrade" to GTK2, which of course means > running "make reconfig" on the new set of configure parameters. > > This "full" compile gave the following warning, which did no

Compile warning -Wmaybe-uninitialized in terminal.c at or maybe before 8.0.798

2017-07-28 Fir de Conversatie Tony Mechelynck
gvim with GTK3 GUI was so untractable recently on my new openSUSE 42.3 system that I decided to "downgrade" to GTK2, which of course means running "make reconfig" on the new set of configure parameters. This "full" compile gave the following warning, which did not prevent the generation of an (at

Re: Compile warning on windows after patch 276

2014-05-09 Fir de Conversatie Bram Moolenaar
Charles Cooper wrote: > Compiling Vim 7.4.282 on windows produces a warning due to some of the > changes in patch 276. > > ex_cmds.c(1554) : warning C4101: 'is_fish_shell' : unreferenced local variable > > The warning can be eliminated by moving the declaration of is_fish_shell to > be immedi

Compile warning on windows after patch 276

2014-05-08 Fir de Conversatie Charles Cooper
Compiling Vim 7.4.282 on windows produces a warning due to some of the changes in patch 276. ex_cmds.c(1554) : warning C4101: 'is_fish_shell' : unreferenced local variable The warning can be eliminated by moving the declaration of is_fish_shell to be immediately after the #if, or enclosing the

Re: Another compile warning

2013-05-30 Fir de Conversatie James McCoy
On May 30, 2013 11:50 AM, "Bram Moolenaar" wrote: > > > Elias Diem wrote: > > > I get another compile warning: > > > > --- > > In file included from regexp.c:7811:0: > > regexp_nfa.c: In function ‘addstate’:

Re: Another compile warning

2013-05-30 Fir de Conversatie Elias Diem
On 2013-05-30, Bram Moolenaar wrote: > I wonder why it doesn't complain about save_lpos. Well, right now I wonder too. -- Greetings Elias -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information,

Re: Another compile warning

2013-05-30 Fir de Conversatie Bram Moolenaar
Elias Diem wrote: > I get another compile warning: > > --- > In file included from regexp.c:7811:0: > regexp_nfa.c: In function ‘addstate’: > regexp_nfa.c:2820:36: warning: ‘save_ptr’ may be used uninitialized in this > func

Another compile warning

2013-05-30 Fir de Conversatie Elias Diem
Hi there I get another compile warning: --- In file included from regexp.c:7811:0: regexp_nfa.c: In function ‘addstate’: regexp_nfa.c:2820:36: warning: ‘save_ptr’ may be used uninitialized in this function [-Wuninitialized

Re: Compile warning.

2013-05-25 Fir de Conversatie Bram Moolenaar
Elias Diem wrote: > I get a compiler warning for regexp_nfa.c. > > > gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/in

Compile warning.

2013-05-25 Fir de Conversatie Elias Diem
Hello all, I get a compiler warning for regexp_nfa.c. gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0

Re: compile warning (probably harmless)

2010-07-24 Fir de Conversatie Tony Mechelynck
On 24/07/10 20:58, Bram Moolenaar wrote: Tony Mechelynck wrote: Compiling changeset d680c97481c1 dated Sat Jul 24 16:19:44 2010 +0200 with Huge features [...] pty.c: In function ‘OpenPTY’: pty.c:295:5: warning: call to function ‘ptsname’ without a real prototype pty.c:281:15: note: ‘ptsname’

Re: compile warning (probably harmless)

2010-07-24 Fir de Conversatie Bram Moolenaar
Tony Mechelynck wrote: > Compiling changeset d680c97481c1 dated Sat Jul 24 16:19:44 2010 +0200 > with Huge features > > [...] > pty.c: In function ‘OpenPTY’: > pty.c:295:5: warning: call to function ‘ptsname’ without a real prototype > pty.c:281:15: note: ‘ptsname’ was declared here > [...] Doe

compile warning (probably harmless)

2010-07-24 Fir de Conversatie Tony Mechelynck
Compiling changeset d680c97481c1 dated Sat Jul 24 16:19:44 2010 +0200 with Huge features [...] pty.c: In function ‘OpenPTY’: pty.c:295:5: warning: call to function ‘ptsname’ without a real prototype pty.c:281:15: note: ‘ptsname’ was declared here [...] Best regards, Tony. -- Military justice is

Re: Vim 7.3a compile warning (undo.c:1265) 'uhp' may be used uninitialized

2010-05-30 Fir de Conversatie Dominique Pellé
Bram Moolenaar wrote: > Tony Mechelynck wrote: > >> Compiling vim 7.3a (huge) at changeset aa6412cab544 (2010-15-29 20:33:07 >> +0200) on Linux using gcc 4.4.1 >> >>  > undo.c: In function ‘u_read_undo’: >>  > undo.c:1265: warning: ‘uhp’ may be used uninitialized in this function >> >> I don't fee

Re: Vim 7.3a compile warning (undo.c:1265) 'uhp' may be used uninitialized

2010-05-30 Fir de Conversatie Bram Moolenaar
Tony Mechelynck wrote: > Compiling vim 7.3a (huge) at changeset aa6412cab544 (2010-15-29 20:33:07 > +0200) on Linux using gcc 4.4.1 > > > undo.c: In function ‘u_read_undo’: > > undo.c:1265: warning: ‘uhp’ may be used uninitialized in this function > > I don't feel qualified to determine with

Vim 7.3a compile warning (undo.c:1265) 'uhp' may be used uninitialized

2010-05-29 Fir de Conversatie Tony Mechelynck
Compiling vim 7.3a (huge) at changeset aa6412cab544 (2010-15-29 20:33:07 +0200) on Linux using gcc 4.4.1 > undo.c: In function ‘u_read_undo’: > undo.c:1265: warning: ‘uhp’ may be used uninitialized in this function I don't feel qualified to determine with certainty whether or not that warning

Re: Compile warning: missing sentinel in function call

2009-05-18 Fir de Conversatie Mike Williams
On 15/05/2009 20:17, Dominique Pellé wrote: > On Fri, May 15, 2009 at 8:23 PM, Bram Moolenaar wrote: > >> Dasn wrote: >> >>> Hi, when compiling 7.2-1-173 on OpenBSD, I got: >>> if_cscope.c: In function `cs_create_connection': if_cscope.c:997: warning: missing sentinel in function call

Re: Compile warning: missing sentinel in function call

2009-05-15 Fir de Conversatie Dominique Pellé
On Fri, May 15, 2009 at 8:23 PM, Bram Moolenaar wrote: > Dasn wrote: > >> Hi, when compiling 7.2-1-173 on OpenBSD, I got: >> >> > if_cscope.c: In function `cs_create_connection': >> > if_cscope.c:997: warning: missing sentinel in function call >> >> Not a big problem, should be easy to fix: >> >

Re: Compile warning: missing sentinel in function call

2009-05-15 Fir de Conversatie Bram Moolenaar
Dasn wrote: > Hi, when compiling 7.2-1-173 on OpenBSD, I got: > > > if_cscope.c: In function `cs_create_connection': > > if_cscope.c:997: warning: missing sentinel in function call > > Not a big problem, should be easy to fix: > > *** if_cscope.c 22 Apr 2009 14:25:01 - 1.36 > --- if_

Compile warning: missing sentinel in function call

2009-05-14 Fir de Conversatie Dasn
Hi, when compiling 7.2-1-173 on OpenBSD, I got: > if_cscope.c: In function `cs_create_connection': > if_cscope.c:997: warning: missing sentinel in function call Not a big problem, should be easy to fix: *** if_cscope.c 22 Apr 2009 14:25:01 - 1.36 --- if_cscope.c 14 May 2009 23:07:54 -0