From: Thomas Monjalon <thomas@monjalon.net>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix clang build with intrinsics forced
Date: Thu, 17 Jan 2019 17:54:20 +0100 [thread overview]
Message-ID: <1855733.j2fUxzXNtQ@xps> (raw)
In-Reply-To: <20190115112939.8780-1-i.maximets@samsung.com>
15/01/2019 12:29, Ilya Maximets:
> This fixes x86_64-native-linuxapp-clang build with
> CONFIG_RTE_FORCE_INTRINSICS=y:
>
> include/generic/rte_atomic.h:218:9: error:
> implicit declaration of function '__atomic_exchange_2'
> is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>
> include/generic/rte_atomic.h:501:9: error:
> implicit declaration of function '__atomic_exchange_4'
> is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>
> include/generic/rte_atomic.h:783:9: error:
> implicit declaration of function '__atomic_exchange_8'
> is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>
> We didn't caught this issue previously on other platforms because
> CONFIG_RTE_FORCE_INTRINSICS enabled by default only for armv8.
>
> Fixes: 7bdccb93078e ("eal: fix ARM build with clang")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
Applied, thanks
prev parent reply other threads:[~2019-01-17 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190115112946eucas1p22fa0b405d8cfe1feae7426a9b37857b1@eucas1p2.samsung.com>
2019-01-15 11:29 ` Ilya Maximets
2019-01-17 16:54 ` 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=1855733.j2fUxzXNtQ@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.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 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).