DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
	"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"viktorin@rehivetech.com" <viktorin@rehivetech.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Gavin Hu <Gavin.Hu@arm.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] aarch32 compilation
Date: Wed, 6 May 2020 13:54:26 +0000	[thread overview]
Message-ID: <HE1PR0801MB202532D1CC320A1FBE039EB59EA40@HE1PR0801MB2025.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <e9ff5606-50e6-25ea-6800-a6cc1ed1a1f3@intel.com>


> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Wednesday, May 6, 2020 6:14 PM
> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; wenzhuo.lu@intel.com;
> konstantin.ananyev@intel.com; jerinj@marvell.com;
> viktorin@rehivetech.com
> Cc: dev@dpdk.org; Gavin Hu <Gavin.Hu@arm.com>; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; juraj.linkes@pantheon.tech; nd
> <nd@arm.com>
> Subject: Re: [dpdk-dev] [PATCH 0/3] aarch32 compilation
> 
> On 5/6/2020 9:09 AM, Ruifeng Wang wrote:
> >
> >> -----Original Message-----
> >> From: Ferruh Yigit <ferruh.yigit@intel.com>
> >> Sent: Friday, May 1, 2020 11:07 PM
> >> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; wenzhuo.lu@intel.com;
> >> konstantin.ananyev@intel.com; jerinj@marvell.com;
> >> viktorin@rehivetech.com
> >> Cc: dev@dpdk.org; Gavin Hu <Gavin.Hu@arm.com>; Honnappa
> Nagarahalli
> >> <Honnappa.Nagarahalli@arm.com>; juraj.linkes@pantheon.tech; nd
> >> <nd@arm.com>
> >> Subject: Re: [dpdk-dev] [PATCH 0/3] aarch32 compilation
> >>
> >> On 4/24/2020 7:50 AM, Ruifeng Wang wrote:
> >>> Build aarch32 binary on aarch64 platform hit issues with l3fwd [1]
> >>> and ixgbe PMD [2]. This patch set is to fix these.
> >>>
> >>> When building with make, please refer to guide:
> >>> http://patches.dpdk.org/patch/62820/
> >>>
> >>> When building with meson, requires series:
> >>> http://patches.dpdk.org/cover/68534/
> >>>
> >>> [1] https://mails.dpdk.org/archives/dev/2020-April/162673.html
> >>> [2] https://mails.dpdk.org/archives/dev/2020-April/163846.html
> >>>
> >>>
> >>> Ruifeng Wang (3):
> >>>   arch/arm: add vcopyq intrinsic for aarch32
> >>>   net/ixgbe: add support for aarch32
> >>>   net/ixgbe: fix include of vector header file
> >>>
> >>
> >> Not directly related to this patch but since you are fixing aarch32
> >> compilation, I am getting following -Wcast-align warnings [1] while cross
> building with:
> >> arm-linux-gcc.br_real (Buildroot 2020.02-00011-g7ea8a52) 9.3.0
> >>
> > I got the same warnings with arm-linux-gnueabihf-gcc. The warnings
> spread in many different files.
> > It is because armv7a/aarch32 puts strict align requirement.
> > We can first make it compile. And clean up such warnings in next step?
> 
> Sure.
> 
> I thought it would break the build, aren't we using -Werror for the target?
Currently, "RTE_DEVEL_BUILD=n" is needed for armv7 build.
http://patches.dpdk.org/patch/62820/

> 
> >
> >>
> >> [1]
> >> .../lib/librte_eal/linux/eal_vfio_mp_sync.c: In function ‘vfio_mp_primary’:
> >> .../lib/librte_eal/linux/eal_vfio_mp_sync.c:31:28: warning: cast
> >> increases required alignment of target type [-Wcast-align]
> >>    31 |  struct vfio_mp_param *r = (struct vfio_mp_param *)reply.param;
> >>       |                            ^
> >> .../lib/librte_eal/linux/eal_vfio_mp_sync.c:33:3: warning: cast
> >> increases required alignment of target type [-Wcast-align]
> >>    33 |   (const struct vfio_mp_param *)msg->param;
> >>       |   ^
> >> .../lib/librte_eal/linux/eal_vfio.c: In function ‘vfio_open_group_fd’:
> >> .../lib/librte_eal/linux/eal_vfio.c:269:28: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>   269 |  struct vfio_mp_param *p = (struct vfio_mp_param
> *)mp_req.param;
> >>       |                            ^
> >> .../lib/librte_eal/linux/eal_vfio.c:316:7: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>   316 |   p = (struct vfio_mp_param *)mp_rep->param;
> >>       |       ^
> >>   CC eal_common_class.o
> >> .../lib/librte_eal/linux/eal_vfio.c: In function
> ‘vfio_sync_default_container’:
> >> .../lib/librte_eal/linux/eal_vfio.c:627:28: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>   627 |  struct vfio_mp_param *p = (struct vfio_mp_param
> *)mp_req.param;
> >>       |                            ^
> >> .../lib/librte_eal/linux/eal_vfio.c:652:7: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>   652 |   p = (struct vfio_mp_param *)mp_rep->param;
> >>       |       ^
> >> .../lib/librte_eal/linux/eal_vfio.c: In function
> ‘vfio_get_default_container_fd’:
> >> .../lib/librte_eal/linux/eal_vfio.c:1094:28: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>  1094 |  struct vfio_mp_param *p = (struct vfio_mp_param
> *)mp_req.param;
> >>       |                            ^
> >> .../lib/librte_eal/linux/eal_vfio.c:1116:7: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>  1116 |   p = (struct vfio_mp_param *)mp_rep->param;
> >>       |       ^
> >>   CC eal_common_bus.o
> >> .../lib/librte_eal/linux/eal_vfio.c: In function ‘rte_vfio_get_container_fd’:
> >> .../lib/librte_eal/linux/eal_vfio.c:1202:28: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>  1202 |  struct vfio_mp_param *p = (struct vfio_mp_param
> *)mp_req.param;
> >>       |                            ^
> >> .../lib/librte_eal/linux/eal_vfio.c:1248:7: warning: cast increases
> >> required alignment of target type [-Wcast-align]
> >>  1248 |   p = (struct vfio_mp_param *)mp_rep->param;
> >>       |       ^


  reply	other threads:[~2020-05-06 13:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  6:50 Ruifeng Wang
2020-04-24  6:50 ` [dpdk-dev] [PATCH 1/3] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-05-01 14:55   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-04-24  6:50 ` [dpdk-dev] [PATCH 2/3] net/ixgbe: add support " Ruifeng Wang
2020-05-01 14:59   ` Ferruh Yigit
2020-05-06  7:54     ` Ruifeng Wang
2020-04-24  6:50 ` [dpdk-dev] [PATCH 3/3] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-05-01 15:06 ` [dpdk-dev] [PATCH 0/3] aarch32 compilation Ferruh Yigit
2020-05-06  8:09   ` Ruifeng Wang
2020-05-06 10:14     ` Ferruh Yigit
2020-05-06 13:54       ` Ruifeng Wang [this message]
2020-05-06 14:14         ` Ferruh Yigit
2020-05-06 14:36           ` Ruifeng Wang
2020-06-23  6:58 ` [dpdk-dev] [PATCH v2 0/4] " Ruifeng Wang
2020-06-23  6:58   ` [dpdk-dev] [PATCH v2 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-23  6:58   ` [dpdk-dev] [PATCH v2 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-23  8:37     ` David Marchand
2020-06-23  8:59       ` Ruifeng Wang
2020-06-23  6:58   ` [dpdk-dev] [PATCH v2 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-23  6:58   ` [dpdk-dev] [PATCH v2 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-24  7:10 ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ruifeng Wang
2020-06-24  7:10   ` [dpdk-dev] [PATCH v3 1/4] arch/arm: add vcopyq intrinsic for aarch32 Ruifeng Wang
2020-06-24  7:10   ` [dpdk-dev] [PATCH v3 2/4] net/ixgbe: add support " Ruifeng Wang
2020-06-24  7:10   ` [dpdk-dev] [PATCH v3 3/4] net/ixgbe: fix include of vector header file Ruifeng Wang
2020-06-24  7:10   ` [dpdk-dev] [PATCH v3 4/4] net/i40e: add support for aarch32 Ruifeng Wang
2020-06-26 13:44   ` [dpdk-dev] [PATCH v3 0/4] aarch32 compilation Ferruh Yigit

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=HE1PR0801MB202532D1CC320A1FBE039EB59EA40@HE1PR0801MB2025.eurprd08.prod.outlook.com \
    --to=ruifeng.wang@arm.com \
    --cc=Gavin.Hu@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=konstantin.ananyev@intel.com \
    --cc=nd@arm.com \
    --cc=viktorin@rehivetech.com \
    --cc=wenzhuo.lu@intel.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).