Re: gcc 10.1 warnings

2020-05-10 Fir de Conversatie John Marriott
On 10-May-2020 21:44, Bram Moolenaar wrote: I included Ken's patch, because it is the simplest. Please check that it works. Hi Bram, Ken's patch works for me. Cheers John -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are r

Re: gcc 10.1 warnings

2020-05-10 Fir de Conversatie Bram Moolenaar
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 :-) I included Ken's patch, because it is

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

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

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_

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

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