From: David Marchand <david.marchand@redhat.com>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: "Ferruh Yigit" <ferruh.yigit@intel.com>, dev <dev@dpdk.org>,
"Michał Krawczyk" <mk@semihalf.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Tzalik, Guy" <gtzalik@amazon.com>,
"Evgeny Schemeilin" <evgenys@amazon.com>,
"Igor Chauskin" <igorch@amazon.com>,
"Andrew Rybchenko" <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3
Date: Wed, 6 May 2020 11:35:48 +0200 [thread overview]
Message-ID: <CAJFAV8wc1Z2S9f1iU1ZyQNztpkCQ3-Quk2Fi+6MAZoLy6fcsww@mail.gmail.com> (raw)
In-Reply-To: <dbe1ed1f-c217-e7aa-2b9c-e64cbf799ec6@linux.vnet.ibm.com>
On Tue, May 5, 2020 at 10:28 PM David Christensen
<drc@linux.vnet.ibm.com> wrote:
>
>
> >> The rte_altivec.h is related to another open patch required to build on
> >> POWER systems (http://patches.dpdk.org/patch/69605/) that's waiting to
> >> be accepted. You may not have encountered it if you're not building the
> >> MLX5 PMD which has additional library requirements.
> >
> > Is there a point in having two patches?
>
> The address different problems. This patch addresses a build issue with
> gcc in Ubuntu 20.04, the other patch is related to the new trace library
> that uses boolean values from stdbool.h (or the use of the --std=c11
> build option) that causes a build error on POWER systems because of
> altivec definitions.
Ok, thanks.
WRT the conflict on the other ppc patch, no need for a new version.
Though it is probably worth backporting if it is a problem with gcc 9.x.
WDYT?
I can add a Cc: stable@dpdk.org when applying.
--
David Marchand
next prev parent reply other threads:[~2020-05-06 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 17:45 [dpdk-dev] [PATCH] eal: fix rte_memcpy build on ppc with gcc 9.3 David Christensen
2020-05-04 21:03 ` [dpdk-dev] [PATCH v2] " David Christensen
2020-05-05 10:33 ` Ferruh Yigit
2020-05-05 16:32 ` David Christensen
2020-05-05 16:41 ` David Marchand
2020-05-05 20:28 ` David Christensen
2020-05-06 9:35 ` David Marchand [this message]
2020-05-06 15:59 ` David Christensen
2020-05-05 18:42 ` Ferruh Yigit
2020-05-05 20:37 ` David Christensen
2020-05-06 9:23 ` Ferruh Yigit
2020-05-06 16:13 ` David Marchand
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=CAJFAV8wc1Z2S9f1iU1ZyQNztpkCQ3-Quk2Fi+6MAZoLy6fcsww@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.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 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.