From: dwilder <dwilder@us.ibm.com>
To: dev@dpdk.org
Subject: [dpdk-dev] ppc64: fix compilation of when AltiVec is enabled
Date: Wed, 05 Sep 2018 14:05:07 -0700 [thread overview]
Message-ID: <a321a8a1bf351f126e36a24659e73013@linux.vnet.ibm.com> (raw)
Hi Christian
I am new to the list thus was unable to reply directly to your post:
[PATCH v2] ppc64: fix compilation of when AltiVec is enabled
I reproduce the build error on my ppc64le box and verified that your V2
patch corrects the build failure on both RHEL 7.5 and Ubuntu 18.04.
Thanks for the patch, apologies for the very slow response.
PS: I ran this past our Power tools team. For now the best practice is
to #undef bool, vector, pixel after including altivec.h when compiled
for C++ or ANSI C11. A patch to gcc for this issue has been proposed
to solve this issue, but it needs to be validated on a Linux
distribution. If this works out it will show up in GCC 9.
Regards
David
reply other threads:[~2018-09-05 21:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a321a8a1bf351f126e36a24659e73013@linux.vnet.ibm.com \
--to=dwilder@us.ibm.com \
--cc=dev@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).