From: Thomas Monjalon <thomas@monjalon.net>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
Ali Alnubani <alialnu@oss.nvidia.com>
Cc: John McNamara <john.mcnamara@intel.com>,
Ian Betts <ian.betts@intel.com>,
Tomasz Kulasek <tomaszx.kulasek@intel.com>,
dev@dpdk.org,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] examples/performance-thread: fix build issue with clang 12.0.1
Date: Fri, 27 Aug 2021 13:36:09 +0200 [thread overview]
Message-ID: <3223668.kHc7HdNlAC@thomas> (raw)
In-Reply-To: <DM4PR12MB5167D24F09332BF32FA21892DAC09@DM4PR12MB5167.namprd12.prod.outlook.com>
19/08/2021 09:09, Ali Alnubani:
> From: jerinj@marvell.com <jerinj@marvell.com>
> > In clang 12.0.1 version, the use of pthread_yield() deprecated, use
> > sched_yield() instead.
> >
> > log:
> >
> > Compiling C object
> > examples/dpdk-pthread_shim.p/performance-
> > thread_pthread_shim_main.c.o
> > ../examples/performance-thread/pthread_shim/main.c: In function
> > 'helloworld_pthread':
> > ../examples/performance-thread/pthread_shim/main.c:75:9: warning:
> > 'pthread_yield' is deprecated: pthread_yield is deprecated, use sched_yield
> > instead [-Wdeprecated-declarations]
> >
> > Fixes: 433ba6228f9a ("examples/performance-thread: add pthread_shim
> > app")
adding Cc: stable for other branches.
> >
> > Bugzilla ID: 745
> >
> > Cc: alialnu@oss.nvidia.com
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
>
> I think this issue might be specific to Fedora Rawhide's build of clang 12.0.1, see my comment in the ticket:
> https://bugs.dpdk.org/show_bug.cgi?id=745#c3
I hit the same issue on Arch Linux.
> Tested-by: Ali Alnubani <alialnu@nvidia.com>
>
> Thanks Jerin.
Applied, thanks.
prev parent reply other threads:[~2021-08-27 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 13:19 jerinj
2021-08-19 7:09 ` Ali Alnubani
2021-08-27 11:36 ` 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=3223668.kHc7HdNlAC@thomas \
--to=thomas@monjalon.net \
--cc=alialnu@oss.nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ian.betts@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=tomaszx.kulasek@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).