From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: Jeff Guo <jia.guo@intel.com>, Haiyue Wang <haiyue.wang@intel.com>,
Alvin Zhang <alvinx.zhang@intel.com>, dev <dev@dpdk.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
nd <nd@arm.com>, Ruifeng Wang <ruifeng.wang@arm.com>,
Feifei Wang <feifei.wang2@arm.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/igc: fix gcc build for optimization level 0
Date: Fri, 27 Nov 2020 10:02:22 +0100 [thread overview]
Message-ID: <CAJFAV8x_8=z8G-_TVuGEABq116_kQFE05BxwdCD=Q7j4w1=-EA@mail.gmail.com> (raw)
In-Reply-To: <20201127080903.26817-3-ruifeng.wang@arm.com>
On Fri, Nov 27, 2020 at 9:10 AM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
>
> Gcc build with '-O0' failed for:
> ../drivers/net/igc/base/igc_api.c
> Assembler messages:
> 29: Error: selected processor does not support `casp x0,x1,x2,x3,[x4]'
> 82: Error: selected processor does not support `caspa x0,x1,x2,x3,[x4]'
> 135: Error: selected processor does not support `caspl x0,x1,x2,x3,[x4]'
> 188: Error: selected processor does not support `caspal x0,x1,x2,x3,[x4]'
>
> This is due to c_args not been passed to meson.
>
> Fixes: 8cb7c57d9b3c ("net/igc: support device initialization")
> Cc: alvinx.zhang@intel.com
>
> Reported-by: Feifei Wang <feifei.wang2@arm.com>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
I did not get to reproduce it yet (get an error on first patch...).
The patch looks fine but I fear some compilation problems since a lot
of base drivers filter cflags.
Still waiting for CI results...
Bruce,Ferruh,
Wdyt?
--
David Marchand
next prev parent reply other threads:[~2020-11-27 9:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:09 [dpdk-dev] [PATCH 0/2] gcc build fix Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 1/2] eal/arm: fix gcc build for optimization level 0 Ruifeng Wang
2020-11-27 8:39 ` David Marchand
2020-11-27 8:51 ` Jerin Jacob
2020-11-27 9:25 ` David Marchand
2020-11-27 9:33 ` Jerin Jacob
2020-11-27 9:45 ` David Marchand
2020-11-27 10:05 ` Ruifeng Wang
2020-11-27 10:28 ` Jerin Jacob
2020-11-27 9:39 ` Andrew Rybchenko
2020-11-27 9:36 ` Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 2/2] net/igc: " Ruifeng Wang
2020-11-27 8:53 ` Jerin Jacob
2020-11-27 9:02 ` David Marchand [this message]
2020-11-27 12:13 ` David Marchand
2020-11-27 14:50 ` Wang, Haiyue
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 0/2] gcc build fix Ruifeng Wang
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 1/2] eal/arm: fix gcc build for optimization level 0 Ruifeng Wang
2020-11-27 13:03 ` Ruifeng Wang
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 2/2] net/igc: " Ruifeng Wang
2020-11-27 13:35 ` [dpdk-dev] [PATCH v2 0/2] gcc build fix Thomas Monjalon
2020-11-27 14:08 ` Ruifeng Wang
2020-11-27 16:03 ` [dpdk-dev] [PATCH " Thomas Monjalon
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='CAJFAV8x_8=z8G-_TVuGEABq116_kQFE05BxwdCD=Q7j4w1=-EA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=alvinx.zhang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=feifei.wang2@arm.com \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jia.guo@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).