[dpdk-dev] [Bug 421] gcc 10.0.1 stringops-overflow warnings

[dpdk-dev] [Bug 421] gcc 10.0.1 stringops-overflow warnings

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=421

            Bug ID: 421
           Summary: gcc 10.0.1 stringops-overflow warnings
           Product: DPDK
           Version: 20.05
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: kevuzaj@gmail.com
  Target Milestone: ---

Created attachment 85
  --> https://bugs.dpdk.org/attachment.cgi?id=85&action=edit
Log of gcc 10.0.1 stringop-overflow warnings

As well as the ones reported for crypto in Bug 394 there are many other
stringop-overflow warnings with gcc 10.0.1 which is the default with Fedora 32.

This is caused by the following documented change since GCC:
https://gcc.gnu.org/gcc-10/changes.html

Enhancements to existing warnings: 
-Wstringop-overflow detects more out-of-bounds stores to member arrays
including zero-length arrays, dynamically allocated objects and variable length
arrays, as well as more instances of reads of unterminated character arrays by
string built-in functions. The warning also detects out-of-bounds accesses by
calls to user-defined functions declared with the new attribute access. 

The following files trigger have these warnings. Full log of warnings attached.

../drivers/crypto/caam_jr/caam_jr_pvt.h
../drivers/crypto/ccp/ccp_crypto.h
../drivers/crypto/dpaa_sec/dpaa_sec.h
../drivers/crypto/virtio/virtio_cryptodev.h
../drivers/net/enic/base/vnic_dev.c
../drivers/net/iavf/../../common/iavf/virtchnl.h
../drivers/net/ice/base/ice_adminq_cmd.h
../drivers/net/mlx4/mlx4_rxtx.c
../drivers/net/qede/base/ecore_mcp.c
../lib/librte_cryptodev/rte_cryptodev.h
../lib/librte_pipeline/rte_table_action.c

Some of these are easy to spot as false positives because of dynamic memory
allocation. Others seem to be too but would need component maintainers to
confirm. Can add individual Bugs per component if needed.

Proposed solution is to add -Wno-stringop-overflow flag at top level.

-- 
You are receiving this mail because:
You are the assignee for the bug.