Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie Ken Takata
Hi, 2020/5/10 Sun 6:38:41 UTC+9 John Marriott wrote: > > > On 10-May-2020 07:11, Bram Moolenaar wrote: > > Any specified reason you exclude clang here? I thought it was using the > > same runtime library. > > > > > Ah no. It looks like I pinched too much from stackoverflow. Whoops sorry > :

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie John Marriott
On 10-May-2020 07:11, Bram Moolenaar wrote: Any specified reason you exclude clang here? I thought it was using the same runtime library. Ah no. It looks like I pinched too much from stackoverflow. Whoops sorry :-) -- -- You received this message from the "vim_dev" maillist. Do not top-pos

Patch 8.2.0726

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0726 Problem:Vim9: leaking memory when calling not compiled :def function. Solution: Check if function is compiled earlier. Files: src/vim9execute.c *** ../vim-8.2.0725/src/vim9execute.c 2020-05-09 22:50:04.755323771 +0200 --- src/vim9execute.c 2020-05-09 23:19:02.15356

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie Bram Moolenaar
John Marriott wrote: > However, putting the definitions around some ifdefs works for me, like > so (see attached): > > #ifdef _WIN64 > typedef unsigned __int64    long_u; > typedef         __int64    long_i; > # if defined(__GNUC__) && !defined(__clang__) Any specified reason you exclude clan

Patch 8.2.0725

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0725 Problem:Vim9: cannot call a function declared later in Vim9 script. Solution: Make two passes through the script file. Files: src/scriptfile.c, src/proto/scriptfile.pro, src/vim9script.c, src/vim9compile.c, src/vim9execute.c, src/proto/vim9compile.pro,

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie John Marriott
On 09-May-2020 21:06, Ken Takata wrote: Hi John, 2020/5/9 Sat 16:30:42 UTC+9 John Marriott wrote: Hi All, After cleaning my vim source repo and rebuilding with the brand new gcc 10.1 (mingw64), I get these warnings: gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_

Patch 8.2.0724

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0724 Problem:Vim9: appending to buffer/window/tab variable not tested Solution: Add a test. Files: src/testdir/test_vim9_script.vim *** ../vim-8.2.0723/src/testdir/test_vim9_script.vim2020-05-07 14:07:19.952220393 +0200 --- src/testdir/test_vim9_script.vim2020-05-0

Patch 8.2.0723

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0723 Problem:Vim9: nested constant expression not evaluated compile time. Solution: Use compile_expr1() for parenthesis. Files: src/vim9compile.c, src/testdir/test_vim9_disassemble.vim *** ../vim-8.2.0722/src/vim9compile.c 2020-05-09 17:35:50.052198310 +0200 --- src/vim9c

Patch 8.2.0722

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0722 Problem:Vim9: not handling constant expression for elseif. Solution: Use postponed constants. Delete the code for evaluating a constant expression. Files: src/vim9compile.c *** ../vim-8.2.0721/src/vim9compile.c 2020-05-09 16:44:18.946423824 +0200 --- src

Patch 8.2.0721

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0721 Problem:Vim9: leaking memory when skipping. Solution: Disable skipping in generate_ppconst(). Files: src/vim9compile.c *** ../vim-8.2.0720/src/vim9compile.c 2020-05-09 15:43:58.322878209 +0200 --- src/vim9compile.c 2020-05-09 16:43:09.214617402 +0200 **

Patch 8.2.0720

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0720 Problem:Occasional exit when encountering an X error. (Manfred Lotz) Solution: On an X error do not exit, do preserve files. Files: src/os_unix.c *** ../vim-8.2.0719/src/os_unix.c 2020-04-28 21:58:25.174049447 +0200 --- src/os_unix.c 2020-05-09 16:08:34.461

Patch 8.2.0719

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0719 Problem:Vim9: more expressions can be evaluated at compile time Solution: Recognize has('name'). Files: src/vim9compile.c, src/testdir/test_vim9_disassemble.vim, src/testdir/test_vim9_expr.vim *** ../vim-8.2.0718/src/vim9compile.c 2020-05-08 19:10:30.7823

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie Bram Moolenaar
John Marriott wrote: > After cleaning my vim source repo and rebuilding with the brand new gcc > 10.1 (mingw64), I get these warnings: > > gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 > -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -DFEAT_GUI_MSWIN > -DFEAT_CLIPBOARD -pipe

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie Ken Takata
Hi, 2020/5/9 Sat 20:06:48 UTC+9 Ken Takata wrote: > > Hi John, > > 2020/5/9 Sat 16:30:42 UTC+9 John Marriott wrote: >> >> Hi All, >> >> After cleaning my vim source repo and rebuilding with the brand new gcc >> 10.1 (mingw64), I get these warnings: >> >> gcc -c -I. -Iproto -DWIN32 -DWINVER=0x

Patch 8.2.0718

2020-05-09 Fir de Conversatie Bram Moolenaar
Patch 8.2.0718 Problem:Gcc warning for returning pointer to local variable. (John Marriott) Solution: Return another pointer. Files: src/evalvars.c *** ../vim-8.2.0717/src/evalvars.c 2020-05-01 15:44:24.539895251 +0200 --- src/evalvars.c 2020-05-09 13:03:45.3413

Re: gcc 10.1 warnings

2020-05-09 Fir de Conversatie Ken Takata
Hi John, 2020/5/9 Sat 16:30:42 UTC+9 John Marriott wrote: > > Hi All, > > After cleaning my vim source repo and rebuilding with the brand new gcc > 10.1 (mingw64), I get these warnings: > > gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 > -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE

gcc 10.1 warnings

2020-05-09 Fir de Conversatie John Marriott
Hi All, After cleaning my vim source repo and rebuilding with the brand new gcc 10.1 (mingw64), I get these warnings: gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H -DFEAT_GUI_MSWIN -DFEAT_CLIPBOARD -pipe -march=native -Wall -O3