DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dev@dpdk.org
Cc: drc@linux.vnet.ibm.com, david.marchand@redhat.com,
	jerinjacobk@gmail.com,  orika@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] PPC64: fix boolean type conflict
Date: Tue, 28 Apr 2020 16:38:33 -0500	[thread overview]
Message-ID: <3091eedf-1ea2-b3ba-f7ba-32182dda08e3@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200428165230.22589-1-thinhtr@linux.vnet.ibm.com>

Please, ignore this patch and pull the patches from Ori Kam and David 
Christensen
https://mails.dpdk.org/archives/dev/2020-April/165783.html

Thanks,
Thinh Tran

On 4/28/2020 11:52 AM, Thinh Tran wrote:
> The altivec.h on PPC64 breaks boolean type:
> 
> In file included from ../lib/librte_mempool/rte_mempool_trace_fp.h:18:0,
>                   from ../lib/librte_mempool/rte_mempool.h:54,
>                   from ../lib/librte_mbuf/rte_mbuf.h:38,
>                   from ../lib/librte_net/rte_ether.h:23,
>                   from ../drivers/common/mlx5/mlx5_nl.h:10,
>                   from ../drivers/common/mlx5/mlx5_nl.c:23:
> ../lib/librte_eal/include/rte_trace_point.h: In function
> ‘__rte_trace_point_fp_is_enabled’:
> ../lib/librte_eal/include/rte_trace_point.h:226:9: error: incompatible
> types when returning type ‘int’ but ‘__vector __bool int {aka
> __vector(4) __bool int}’ was expected
>    return false;
> 
> It needs to be redefinded as in the stdbool.h
> 
> 
> Signed-off-by: Thinh Tran <thinhtr@linux.vnet.ibm.com>
> ---
>   drivers/common/mlx5/mlx5_common.h       | 10 ----------
>   drivers/net/mlx4/mlx4_utils.h           | 10 ----------
>   drivers/net/mlx5/mlx5_utils.h           | 10 ----------
>   lib/librte_eal/ppc/include/rte_memcpy.h |  4 ++++
>   4 files changed, 4 insertions(+), 30 deletions(-)
> 
> diff --git a/drivers/common/mlx5/mlx5_common.h b/drivers/common/mlx5/mlx5_common.h
> index 16de1b397..c2d688a9b 100644
> --- a/drivers/common/mlx5/mlx5_common.h
> +++ b/drivers/common/mlx5/mlx5_common.h
> @@ -17,16 +17,6 @@
>   #include "mlx5_prm.h"
> 
> 
> -/*
> - * Compilation workaround for PPC64 when AltiVec is fully enabled, e.g. std=c11.
> - * Otherwise there would be a type conflict between stdbool and altivec.
> - */
> -#if defined(__PPC64__) && !defined(__APPLE_ALTIVEC__)
> -#undef bool
> -/* redefine as in stdbool.h */
> -#define bool _Bool
> -#endif
> -
>   /* Bit-field manipulation. */
>   #define BITFIELD_DECLARE(bf, type, size) \
>   	type bf[(((size_t)(size) / (sizeof(type) * CHAR_BIT)) + \
> diff --git a/drivers/net/mlx4/mlx4_utils.h b/drivers/net/mlx4/mlx4_utils.h
> index b8769562a..095958f3d 100644
> --- a/drivers/net/mlx4/mlx4_utils.h
> +++ b/drivers/net/mlx4/mlx4_utils.h
> @@ -14,16 +14,6 @@
> 
>   #include "mlx4.h"
> 
> -/*
> - * Compilation workaround for PPC64 when AltiVec is fully enabled, e.g. std=c11.
> - * Otherwise there would be a type conflict between stdbool and altivec.
> - */
> -#if defined(__PPC64__) && !defined(__APPLE_ALTIVEC__)
> -#undef bool
> -/* redefine as in stdbool.h */
> -#define bool _Bool
> -#endif
> -
>   extern int mlx4_logtype;
> 
>   #ifdef RTE_LIBRTE_MLX4_DEBUG
> diff --git a/drivers/net/mlx5/mlx5_utils.h b/drivers/net/mlx5/mlx5_utils.h
> index d81ace394..0e016f87c 100644
> --- a/drivers/net/mlx5/mlx5_utils.h
> +++ b/drivers/net/mlx5/mlx5_utils.h
> @@ -21,16 +21,6 @@
>   #include "mlx5_defs.h"
> 
> 
> -/*
> - * Compilation workaround for PPC64 when AltiVec is fully enabled, e.g. std=c11.
> - * Otherwise there would be a type conflict between stdbool and altivec.
> - */
> -#if defined(__PPC64__) && !defined(__APPLE_ALTIVEC__)
> -#undef bool
> -/* redefine as in stdbool.h */
> -#define bool _Bool
> -#endif
> -
>   /* Convert a bit number to the corresponding 64-bit mask */
>   #define MLX5_BITSHIFT(v) (UINT64_C(1) << (v))
> 
> diff --git a/lib/librte_eal/ppc/include/rte_memcpy.h b/lib/librte_eal/ppc/include/rte_memcpy.h
> index 25311ba1d..abeede231 100644
> --- a/lib/librte_eal/ppc/include/rte_memcpy.h
> +++ b/lib/librte_eal/ppc/include/rte_memcpy.h
> @@ -11,6 +11,10 @@
>   /*To include altivec.h, GCC version must  >= 4.8 */
>   #include <altivec.h>
> 
> +/* redefine as in stdbool.h after altivec.h */
> +#undef bool
> +#define bool _Bool
> +
>   #ifdef __cplusplus
>   extern "C" {
>   #endif
> 

      reply	other threads:[~2020-04-28 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 16:52 Thinh Tran
2020-04-28 21:38 ` Thinh Tran [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3091eedf-1ea2-b3ba-f7ba-32182dda08e3@linux.vnet.ibm.com \
    --to=thinhtr@linux.vnet.ibm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=jerinjacobk@gmail.com \
    --cc=orika@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).