avoid AltiVec keyword vectorThe AltiVec header file is defining "vector", except in C++ build.The keyword "vector" may conflict easily.As a rule, it is better to use the alternative keyword "__ve
avoid AltiVec keyword vectorThe AltiVec header file is defining "vector", except in C++ build.The keyword "vector" may conflict easily.As a rule, it is better to use the alternative keyword "__vector",so we will be able to #undef vector after including AltiVec header.Later it may become possible to #undef vector in rte_altivec.hwith a compatibility breakage.Signed-off-by: Thomas Monjalon <[email protected]>Reviewed-by: David Christensen <[email protected]>
show more ...
eal/ppc: use compiler builtins for atomicsReplace existing PPC assembly code for rte_atomicXX ops with compileratomic builtins as previously adopted by DPDK (see [1] and [2]). Thishas the additi
eal/ppc: use compiler builtins for atomicsReplace existing PPC assembly code for rte_atomicXX ops with compileratomic builtins as previously adopted by DPDK (see [1] and [2]). Thishas the additional benefit of resolving a POWER10 build failure due to anoutstanding gcc issue which fails on the existing PPC assembly code [3].[1] https://www.dpdk.org/blog/2021/03/26/dpdk-adopts-the-c11-memory-model/[2] https://doc.dpdk.org/guides/rel_notes/deprecation.html[3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98519Signed-off-by: David Christensen <[email protected]>
eal/ppc: ignore GCC 10 stringop-overflow warningsSuppress gcc warning "warning: writing 16 bytes into a region ofsize 0" for users of the POWER rte_memcpy() function. Existingrte_memcpy() code t
eal/ppc: ignore GCC 10 stringop-overflow warningsSuppress gcc warning "warning: writing 16 bytes into a region ofsize 0" for users of the POWER rte_memcpy() function. Existingrte_memcpy() code takes different code paths based on the actualsize of the move so the warning is already addressed. See alsocommit b5b3ea803e47 ("eal/x86: ignore gcc 10 stringop-overflow warnings")Cc: [email protected]Signed-off-by: David Christensen <[email protected]>
lib: remove librte_ prefix from directory namesThere is no reason for the DPDK libraries to all have 'librte_' prefix onthe directory names. This prefix makes the directory names longer and alsom
lib: remove librte_ prefix from directory namesThere is no reason for the DPDK libraries to all have 'librte_' prefix onthe directory names. This prefix makes the directory names longer and alsomakes it awkward to add features referring to individual libraries in thebuild - should the lib names be specified with or without the prefix.Therefore, we can just remove the library prefix and use the library'sunique name as the directory name, i.e. 'eal' rather than 'librte_eal'Signed-off-by: Bruce Richardson <[email protected]>