patch 9.1.0455: MS-Windows: compiler warning for size_t to int conversion
Commit:
https://github.com/vim/vim/commit/16b63bd002d48fa0b04f27cf3ccca894e14db378
Author: Mike Williams
Date: Sat Jun 1 11:33:40 2024 +0200
patch 9.1.0455: MS-Windows: compiler warning for size_t to int conversion
patch 9.1.0448: compiler warning in eval.c
Commit:
https://github.com/vim/vim/commit/8904d672befb496cf224f01bc042683bb6120e81
Author: Yegappan Lakshmanan
Date: Wed May 29 07:51:50 2024 +0200
patch 9.1.0448: compiler warning in eval.c
Problem: compiler warning in eval.c (after
patch 9.1.0288: MS-Windows: compiler warning for size_t to int conversion
Commit:
https://github.com/vim/vim/commit/72a156b4edfdf1502d421370cf38281c258e3c4a
Author: Mike Williams
Date: Tue Apr 9 22:04:54 2024 +0200
patch 9.1.0288: MS-Windows: compiler warning for size_t to int conversion
patch 9.1.0092: Compiler warning for missing type in scroll_event()
Commit:
https://github.com/vim/vim/commit/c908371aec920b8174e40a1adb73a50e326a5668
Author: Christian Brabandt
Date: Sat Feb 10 13:17:16 2024 +0100
patch 9.1.0092: Compiler warning for missing type in scroll_event
patch 9.0.2175: Compiler warning for uninitialized var
Commit:
https://github.com/vim/vim/commit/38ce1a7ac8da8ac0a8b58a1087f56e62e6fdfaa4
Author: Yegappan Lakshmanan
Date: Mon Dec 18 08:58:29 2023 +0100
patch 9.0.2175: Compiler warning for uninitialized var
Problem: Compiler
Yegappan wrote:
> I am seeing the following compiler warning in userfunc.c:
>
> userfunc.c: In function ‘ex_function’:
> userfunc.c:2612:3: warning: ‘%s’ directive argument is null
> [-Wformat-overflow=]
> 2612 | semsg(_("E1056: expected
Hi,
I am seeing the following compiler warning in userfunc.c:
userfunc.c: In function ‘ex_function’:
userfunc.c:2612:3: warning: ‘%s’ directive argument is null
[-Wformat-overflow=]
2612 | semsg(_("E1056: expected a type: %s")
Christian wrote:
> I see the following compiler warning:
>
> In file included from regexp.c:7939:
> regexp_nfa.c: In function ‘nfa_regmatch’:
> regexp_nfa.c:6519:6: warning: ‘result’ may be used uninitialized in this
> function [-Wmaybe-uninitialized]
>if (result
Bram,
I see the following compiler warning:
In file included from regexp.c:7939:
regexp_nfa.c: In function ‘nfa_regmatch’:
regexp_nfa.c:6519:6: warning: ‘result’ may be used uninitialized in this
function [-Wmaybe-uninitialized]
if (result)
^
This patch fixes it:
diff --git a/src
> Vim-for-Windows developers,
>
> In the file if_ole.cpp, gcc generates a "passing NULL to non-pointer argument
> 3" warning on line number 762:
>
> hr = RegisterActiveObject(
> app,
> MYCLSID,
> NULL, <-
> &app_id);
>
> Microsoft docs say that the
Vim-for-Windows developers,
In the file if_ole.cpp, gcc generates a "passing NULL to non-pointer argument
3" warning on line number 762:
hr = RegisterActiveObject(
app,
MYCLSID,
NULL, <-
&app_id);
Microsoft docs say that the third argument mus
On Tue, Jul 10, 2018 at 3:07 PM, Bram Moolenaar wrote:
>
> Axel Bender wrote:
>
>> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
>> receive the following compiler warning in file undo.c:
>>
>> gcc -c -Iproto -DWIN32 -DWI
Axel Bender wrote:
> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
> receive the following compiler warning in file undo.c:
>
> gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF
> -DFEAT_BIG -DHAVE_STDINT_H -DMS_WIN64
On Mon, Jul 9, 2018 at 9:32 AM, Dominique Pellé
wrote:
> Axel Bender wrote:
>
>> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
>> receive the following compiler warning in file userfunc.c:
>>
>> gcc -c -Iproto -DWIN32 -DWINVE
Axel Bender wrote:
> Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
> receive the following compiler warning in file userfunc.c:
>
> gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF
> -DFEAT_BIG -DHAVE_STDINT_H -DMS_WIN64
Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
receive the following compiler warning in file userfunc.c:
gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF
-DFEAT_BIG -DHAVE_STDINT_H -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H
Compiling gVim 8.1 (latest) on Windows 7 64-bit with MinGW gcc 7.30 64-bit I
receive the following compiler warning in file undo.c:
gcc -c -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF
-DFEAT_BIG -DHAVE_STDINT_H -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H
-DDYNAMIC_GETTEXT
Kazunobu Kuriyama wrote:
> 2016-08-24 2:22 GMT+09:00 Danek Duvall :
>
> > On Tue, Aug 23, 2016 at 06:01:54PM +0900, Kazunobu Kuriyama wrote:
> >
> > > Hi Danek,
> > >
> > > I think that mismatch is not our fault, either.
> >
> > Yeah, that was my thought, but I thought perhaps the Solaris setup
On Wed, Aug 24, 2016 at 07:09:01PM +0900, Kazunobu Kuriyama wrote:
> > I guess I'm a bit surprised that clang didn't show it; I thought it did
> > a better job of finding bad code. I guess that's why we try to have a
> > diverse bundle of compilers. :)
>
> Indeed. And I envy you for the compil
2016-08-24 2:22 GMT+09:00 Danek Duvall :
> On Tue, Aug 23, 2016 at 06:01:54PM +0900, Kazunobu Kuriyama wrote:
>
> > Hi Danek,
> >
> > I think that mismatch is not our fault, either.
>
> Yeah, that was my thought, but I thought perhaps the Solaris setup was
> somehow incorrect. But it really does
On Tue, Aug 23, 2016 at 06:01:54PM +0900, Kazunobu Kuriyama wrote:
> Hi Danek,
>
> I think that mismatch is not our fault, either.
Yeah, that was my thought, but I thought perhaps the Solaris setup was
somehow incorrect. But it really does look like a bug in glib/gtk. I'll
see if I can get a b
2016-08-23 4:45 GMT+09:00 Danek Duvall :
> I'm seeing these warnings when building on Solaris with the Studio
> compilers.
>
> "gui_gtk_f.c", line 507: warning: argument #6 is incompatible with
> prototype:
> prototype: pointer to void :
> "/usr/include/glib-2.0/gobject/gsignal.h"
Danek Duvall wrote:
> I'm also seeing these warnings:
>
> "globals.h", line 371: warning: initializer will be sign-extended: -1
> "globals.h", line 372: warning: initializer will be sign-extended: -1
>
> Hardly surprising since it's taking a negative value and implicitly casting
I'm also seeing these warnings:
"globals.h", line 371: warning: initializer will be sign-extended: -1
"globals.h", line 372: warning: initializer will be sign-extended: -1
Hardly surprising since it's taking a negative value and implicitly casting
to unsigned. But I don't know wh
I'm seeing these warnings when building on Solaris with the Studio
compilers.
"gui_gtk_f.c", line 507: warning: argument #6 is incompatible with
prototype:
prototype: pointer to void :
"/usr/include/glib-2.0/gobject/gsignal.h", line 431
argument : pointer to function(
Tony Mechelynck wrote:
> quickfix.c: In function ‘qf_msg’:
> quickfix.c:2598:2: warning: pointer targets in passing argument 2 of
> ‘vim_strcat’ differ in signedness [-Wpointer-sign]
> vim_strcat(buf, title, IOSIZE);
> ^
> In file included from proto.h:134:0,
> from vim.h:206
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/lib
Anton Lindqvist wrote:
> Hi,
> Compiling commit e0d3797 with GCC and -pedantic gives the following
> warning:
>
> quickfix.c: In function 'qf_init_ext':
> quickfix.c:795: warning: initializer element is not computable at load time
> quickfix.c:795: warning: initializer element is not computable
Hi,
Compiling commit e0d3797 with GCC and -pedantic gives the following
warning:
quickfix.c: In function 'qf_init_ext':
quickfix.c:795: warning: initializer element is not computable at load time
quickfix.c:795: warning: initializer element is not computable at load time
Attached is a patch that
Annoying. ;-)
--
--
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, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" g
On Mon, Feb 22, 2016 at 11:13 PM, Bram Moolenaar wrote:
>
> Tux wrote:
>
>> Well, well.
>
> Sorry, I find it difficult to count beyond 4. :-)
I find that difficult to believe since VI is 6 in roman numerals ;-)
Christ van Willegen
--
--
You received this message from the "vim_dev" maillist.
Tux wrote:
> Well, well.
Sorry, I find it difficult to count beyond 4. :-)
--
FATHER:You killed eight wedding guests in all!
LAUNCELOT: Er, Well ... the thing is ... I thought your son was a lady.
FATHER:I can understand that.
"Monty Python and the Holy Grail" PYTHON
Well, well.
--
--
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, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" gro
Hi,
2016/2/22 Mon 22:32:17 UTC+9 Tony Mechelynck wrote:
> After updating my Vim clone to v7.4.1386, the same message appears in
> both Huge and Tiny:
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o
> ex_
After updating my Vim clone to v7.4.1386, the same message appears in
both Huge and Tiny:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o
ex_cmds2.c
ex_cmds2.c: In function ‘source_pack_plugin’:
ex_cmds2.c:3076
David Fishburn wrote:
> :ver
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 29 2015 11:12:16)
> MS-Windows 32-bit GUI version with OLE support
> Included patches: 1-994
>
>
> ps.c
> option.c
> os_mswin.c
> winclip.c
> os_win32.c
> os_win32.c(679) : warning C4996: 'GetVersionExA': was declar
:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 29 2015 11:12:16)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-994
ps.c
option.c
os_mswin.c
winclip.c
os_win32.c
os_win32.c(679) : warning C4996: 'GetVersionExA': was declared deprecated
C:\Program Files (x86)\Win
Tux wrote:
> Seems to work.
Thanks.
--
Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke
Any sufficiently advanced bug is indistinguishable from a feature.
Rich Kulawiec
///
Seems to work.
--
--
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, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev"
Tony Mechelynck wrote:
> After downloading 7.3.1190 to 7.3.1193, the following warning appears in
> Tiny build but not in Huge:
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
> -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> -o objects/regexp.o regexp.c
After downloading 7.3.1190 to 7.3.1193, the following warning appears in
Tiny build but not in Huge:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -O2
-fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-o objects/regexp.o regexp.c
regexp.c: In function ‘regmatch’:
r
Bram Moolenaar wrote:
>
> Christ van Willegen wrote:
>
>> I get the following during the compilation of Vim:
>>
>>
>> gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
>> -D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
>> ex_cmds2.c: In function 'profile_divide':
>> ex_cm
Christ van Willegen wrote:
> I get the following during the compilation of Vim:
>
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
> -D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
> ex_cmds2.c: In function 'profile_divide':
> ex_cmds2.c:985: warning: incompatible
I get the following during the compilation of Vim:
gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1 -o objects/ex_cmds2.o ex_cmds2.c
ex_cmds2.c: In function 'profile_divide':
ex_cmds2.c:985: warning: incompatible implicit declaration of built-in
function '
On May 30, 2013 1:01 PM, "Bram Moolenaar" wrote:
>
>
> Manuel Ortega wrote:
>
> > I got a compiler warning on OSX 10.8.3 that I've never seen before.
This
> > is while building 7.3.1072. The last vim I built was 7.3.1053 and this
> > warning
Manuel Ortega wrote:
> I got a compiler warning on OSX 10.8.3 that I've never seen before. This
> is while building 7.3.1072. The last vim I built was 7.3.1053 and this
> warning didn't exist then.
>
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNI
I got a compiler warning on OSX 10.8.3 that I've never seen before. This
is while building 7.3.1072. The last vim I built was 7.3.1053 and this
warning didn't exist then.
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -no-cpp-precomp -g -O2
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=
Tony Mechelynck wrote:
> On 26/02/13 19:36, Bram Moolenaar wrote:
> >
> > Patch 7.3.841
> > Problem:When a "cond ? one : two" expression has a subscript it is not
> > parsed correctly. (Andy Wokula)
> > Solution: Handle a subscript also when the type is unknown. (Christian
> >
On 26/02/13 19:36, Bram Moolenaar wrote:
Patch 7.3.841
Problem:When a "cond ? one : two" expression has a subscript it is not
parsed correctly. (Andy Wokula)
Solution: Handle a subscript also when the type is unknown. (Christian
Brabandt)
Files: src/eval.c, src
Bjorn Winckler wrote:
> For the last two weeks or so I've been getting this warning when
> compiling Vim (on Mac OS X):
>
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:593
On 20/02/09 18:02, björn wrote:
> 2009/2/20 Tony Mechelynck:
>> On 20/02/09 13:53, björn wrote:
>>> Hi,
>>>
>>> For the last two weeks or so I've been getting this warning when
>>> compiling Vim (on Mac OS X):
>>>
>>> ex_docmd.c: In function 'do_one_cmd':
>>> ex_docmd.c:5937: warning: 'end' may be
On 20/02/09 17:39, Dominique Pelle wrote:
> björn wrote:
>
>> Hi,
>>
>> For the last two weeks or so I've been getting this warning when
>> compiling Vim (on Mac OS X):
>>
>> ex_docmd.c: In function 'do_one_cmd':
>> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
>> ex_d
2009/2/20 Tony Mechelynck:
>
> On 20/02/09 13:53, björn wrote:
>> Hi,
>>
>> For the last two weeks or so I've been getting this warning when
>> compiling Vim (on Mac OS X):
>>
>> ex_docmd.c: In function 'do_one_cmd':
>> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
>>
On 20/02/09 13:53, björn wrote:
> Hi,
>
> For the last two weeks or so I've been getting this warning when
> compiling Vim (on Mac OS X):
>
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
> ex_docmd.c: In function 'do_one_cmd':
>
björn wrote:
> Hi,
>
> For the last two weeks or so I've been getting this warning when
> compiling Vim (on Mac OS X):
>
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:5937:
On Friday 20 February 2009 6:53 am, björn wrote:
>
> For the last two weeks or so I've been getting this warning when
> compiling Vim (on Mac OS X):
>
> ex_docmd.c: In function 'do_one_cmd':
> ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
> ex_docmd.c: In function 'd
Hi,
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uni
Markus Heidelberg wrote:
> this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
> warning: missing sentinel in function call
Thanks, I'll include it.
--
Lawmakers made it obligatory for everybody to take at least one bath
each week -- on Saturday night.
Tony Mechelynck, 10.05.2008:
> On 09/05/08 22:14, Markus Heidelberg wrote:
> > Conclusion: it is an avoidable warning.
>
> ...but probably not if you compile with GTK1.
Yes, it is. I copmiled with GTK1 and the warning disappeared with this patch.
> I know the authors of GTK1
> have abandoned al
On 09/05/08 22:14, Markus Heidelberg wrote:
> Tony Mechelynck, 09.05.2008:
>> On 09/05/08 09:23, Markus Heidelberg wrote:
>>> this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
>>> warning: missing sentinel in function call
>> I'm using gc
Tony Mechelynck, 09.05.2008:
> On 09/05/08 09:23, Markus Heidelberg wrote:
> >
> > this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
> > warning: missing sentinel in function call
>
> I'm using gcc 4.2.1 (with +multi_byte) and I don'
On 09/05/08 09:23, Markus Heidelberg wrote:
> Hello,
>
> this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
> warning: missing sentinel in function call
>
> Index: src/mbyte.c
> ===
> *** src
Markus Heidelberg, 09.05.2008:
>
> Hello,
>
> this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
> warning: missing sentinel in function call
> ! XSetICValues(((GdkICPrivate*)ic)->xic, XNResetState, XIMPreserveState,
> 0);
> ! XSetICValu
Hello,
this patch fixes following compiler warning (gcc 4.1.2 on GNU/Linux):
warning: missing sentinel in function call
Index: src/mbyte.c
===
*** src/mbyte.c (revision 1007)
--- src/mbyte.c (working copy
Adri Verhoef wrote:
> On Fri, Jan 18, 2008 at 13:29:51 +0100, Bram Moolenaar wrote:
> >
> > Adri Verhoef wrote:
> >
> > > Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
> > >
> > > gui_motif.c: In function 'find_replace_dialog_create':
> > > gui_motif.c:3816: warning: cast
On Fri, Jan 18, 2008 at 13:29:51 +0100, Bram Moolenaar wrote:
>
> Adri Verhoef wrote:
>
> > Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
> >
> > gui_motif.c: In function 'find_replace_dialog_create':
> > gui_motif.c:3816: warning: cast to pointer from integer of different
Adri Verhoef wrote:
> Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
>
> gui_motif.c: In function 'find_replace_dialog_create':
> gui_motif.c:3816: warning: cast to pointer from integer of different size
>
> Installation went fine.
> The warning may not be exclusively tied
Compilation of Vim 7.1.230 on an Alpha processor with Gcc yielded:
gui_motif.c: In function 'find_replace_dialog_create':
gui_motif.c:3816: warning: cast to pointer from integer of different size
Installation went fine.
The warning may not be exclusively tied to Vim 7.1.230, I skipped a few
vers
Mike Williams wrote:
> The diff is against 7.1.116 - the warning appeared after patch 106. The
> warning is:
>
> ops.c(2608) : warning C4018: '>' : signed/unsigned mismatch
I'll include it, thanks.
--
An indication you must be a manager:
You feel sorry for Dilbert's boss.
/// Bram Moolen
Hi,
The diff is against 7.1.116 - the warning appeared after patch 106. The
warning is:
ops.c(2608) : warning C4018: '>' : signed/unsigned mismatch
Enjoy.
Mike
--
Ohgreat,nowthedamspacebardoesn'twork...
--~--~-~--~~~---~--~~
You received this message from the
70 matches
Mail list logo
