From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Hu <gavin.hu@arm.com>
Cc: stable@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] config: fix meson build failure on ThunderX2
Date: Tue, 16 Jul 2019 00:20:26 +0200 [thread overview]
Message-ID: <2079494.8mPjIUjPEx@xps> (raw)
In-Reply-To: <BYAPR18MB2424CA3BCB4DD09C1ECC379EC8F20@BYAPR18MB2424.namprd18.prod.outlook.com>
12/07/2019 13:20, Jerin Jacob Kollanukkaran:
> From: Gavin Hu <gavin.hu@arm.com>
> > Since gcc-8.3(I tried 8.3 and 9.1), the meson build failed on ThunderX2.
> > It got the following compiling errors:
> > /usr/lib/gcc/aarch64-linux-gnu/9/include/arm_neon.h:26493:1: error:
> > inlining failed in call to always_inline ‘vmull_p64’: target specific option
> > mismatch 26493 | vmull_p64 (poly64_t a, poly64_t b)
> >
> > Fixes: 7286c9d7234f ("config: add thunderx2 machine")
> > Cc: jerinj@marvell.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Gavin Hu <gavin.hu@arm.com>
> > Reviewed-by: Phil Yang <phil.yang@arm.com>
> > Reviewed-by: Jingzhao Ni <jingzhao.ni@arm.com>
>
> Thanks Gavin.
> Able to reproduce this issue with gcc 9.1 and proposed patch fixing the issue as well.
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks
prev parent reply other threads:[~2019-07-15 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 11:20 [dpdk-dev] [PATCH] config: fix meson build failure on ThunderX2 Jerin Jacob Kollanukkaran
2019-07-12 16:39 ` Honnappa Nagarahalli
2019-07-15 3:57 ` Jerin Jacob Kollanukkaran
2019-07-15 14:24 ` Honnappa Nagarahalli
2019-07-15 14:34 ` Jerin Jacob Kollanukkaran
2019-07-15 16:04 ` Honnappa Nagarahalli
2019-07-15 22:20 ` Thomas Monjalon [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=2079494.8mPjIUjPEx@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.