From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"roretzla@linux.microsoft.com" <roretzla@linux.microsoft.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
nd <nd@arm.com>
Subject: RE: [RFC] eal: use same atomic intrinsics for gcc and clang
Date: Thu, 16 Feb 2023 06:53:37 +0000 [thread overview]
Message-ID: <AS8PR08MB70805305BB55742FE5827E809EA09@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20230211015622.408487-1-honnappa.nagarahalli@arm.com>
> -----Original Message-----
> From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Sent: Saturday, February 11, 2023 9:56 AM
> To: roretzla@linux.microsoft.com; bruce.richardson@intel.com; mb@smartsharesystems.com
> Cc: dev@dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Ruifeng Wang
> <Ruifeng.Wang@arm.com>; jerinj@marvell.com; nd <nd@arm.com>; stable@dpdk.org;
> pbhagavatula@marvell.com
> Subject: [RFC] eal: use same atomic intrinsics for gcc and clang
>
> The size generic atomic intrinsics generate the same code as the size specific intrinsics
> for gcc. Use size generic intrinsics for both gcc and clang.
>
> Fixes: 7bdccb93078e ("eal: fix ARM build with clang")
> Cc: stable@dpdk.org
> Cc: pbhagavatula@marvell.com
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
Thanks.
next prev parent reply other threads:[~2023-02-16 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 1:56 Honnappa Nagarahalli
2023-02-11 8:04 ` Morten Brørup
2023-02-13 20:01 ` Tyler Retzlaff
2023-02-13 20:13 ` Honnappa Nagarahalli
2023-02-16 6:53 ` Ruifeng Wang [this message]
2023-02-18 1:58 ` [PATCH] " Honnappa Nagarahalli
2023-02-20 7:46 ` 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=AS8PR08MB70805305BB55742FE5827E809EA09@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.com \
--cc=roretzla@linux.microsoft.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).