Re: [dpdk-dev] [PATCH v2] windows: build warnings with clang

2021-12-12 Thread Xueming(Steven) Li
On Wed, 2020-12-09 at 09:30 +, Nick Connolly wrote: > Copying sta...@dpdk.org - given that 20.11 has now been released I > assume this needs to be applied there as well. This patch was ignored due to the backport scanning scripts check commit message from upstream git repo, not mail thread. R

Re: [dpdk-dev] [PATCH v2] windows: build warnings with clang

2020-12-09 Thread Nick Connolly
Copying sta...@dpdk.org - given that 20.11 has now been released I assume this needs to be applied there as well. On 07/12/2020 20:34, Thomas Monjalon wrote: 03/12/2020 01:02, Dmitry Kozlyuk: On Sun, 29 Nov 2020 16:00:24 +, Nick Connolly wrote: Microsoft CRT defines Windows-specific secur

Re: [dpdk-dev] [PATCH v2] windows: build warnings with clang

2020-12-07 Thread Thomas Monjalon
03/12/2020 01:02, Dmitry Kozlyuk: > On Sun, 29 Nov 2020 16:00:24 +, Nick Connolly wrote: > > Microsoft CRT defines Windows-specific secure alternatives to > > standard library functions and triggers warnings when "insecure" > > functions are used [1]. However, calling code already has all > > n

Re: [dpdk-dev] [PATCH v2] windows: build warnings with clang

2020-12-04 Thread Kadam, Pallavi
Hi Nick, Thanks for this patch. Could not see the deprecated warnings anymore. On 11/29/2020 8:00 AM, Nick Connolly wrote: Microsoft CRT defines Windows-specific secure alternatives to standard library functions and triggers warnings when "insecure" functions are used [1]. However, calling code

Re: [dpdk-dev] [PATCH v2] windows: build warnings with clang

2020-12-02 Thread Dmitry Kozlyuk
On Sun, 29 Nov 2020 16:00:24 +, Nick Connolly wrote: > Microsoft CRT defines Windows-specific secure alternatives to > standard library functions and triggers warnings when "insecure" > functions are used [1]. However, calling code already has all > necessary checks around those functions, so t

[dpdk-dev] [PATCH v2] windows: build warnings with clang

2020-11-29 Thread Nick Connolly
Microsoft CRT defines Windows-specific secure alternatives to standard library functions and triggers warnings when "insecure" functions are used [1]. However, calling code already has all necessary checks around those functions, so these warnings are not useful for DPDK. MinGW provides its own CRT