On 6/10/2022 11:39 AM, Morten Brørup wrote:
CAUTION: This message has originated from an External Source. Please use proper
judgment and caution when opening attachments, clicking links, or responding to
this email.
From: Ferruh Yigit [mailto:ferruh.yi...@xilinx.com]
Sent: Friday, 10 June 20
> From: Ferruh Yigit [mailto:ferruh.yi...@xilinx.com]
> Sent: Friday, 10 June 2022 12.13
>
> On 6/8/2022 11:49 PM, Stephen Hemminger wrote:
> > Gcc 12 adds more array bounds checking (good); but it is not smart
> > enough to realize that for small fixed sizes, the bigger move options
> > are not u
On 6/8/2022 11:49 PM, Stephen Hemminger wrote:
Gcc 12 adds more array bounds checking (good); but it is not smart
enough to realize that for small fixed sizes, the bigger move options
are not used.
An example is using rte_memcpy() on a RSS key of 40 bytes may trigger
rte_memcpy complaints from r
08/06/2022 23:49, Stephen Hemminger пишет:
Gcc 12 adds more array bounds checking (good); but it is not smart
enough to realize that for small fixed sizes, the bigger move options
are not used.
An example is using rte_memcpy() on a RSS key of 40 bytes may trigger
rte_memcpy complaints from rte_m
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Thursday, 9 June 2022 00.49
>
> Gcc 12 adds more array bounds checking (good); but it is not smart
> enough to realize that for small fixed sizes, the bigger move options
> are not used.
>
> An example is using rte_memcpy() on
Gcc 12 adds more array bounds checking (good); but it is not smart
enough to realize that for small fixed sizes, the bigger move options
are not used.
An example is using rte_memcpy() on a RSS key of 40 bytes may trigger
rte_memcpy complaints from rte_mov128 reading past end of input.
In order to
6 matches
Mail list logo
