From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B0C77A034F; Wed, 6 May 2020 11:36:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 92A931D70B; Wed, 6 May 2020 11:36:07 +0200 (CEST) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by dpdk.org (Postfix) with ESMTP id 5A11E1D705 for ; Wed, 6 May 2020 11:36:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588757764; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=oXccc+gyfsq6YMG5LFGSMYv//FQvO30O3aX1e5l3tLs=; b=dXB8CcZAZhg4SDhgaaNwCKd61KwjKaYQISvbnu1Vp926/13ZyXa4BdKmi+6J7X/zLn5srR m3SD8vPJyFmFiBNypVMQDIcDGiUpy03DE86q6b66+6KPs6kw3c98OKxr0483wAyWZtzm+I +AQuAehNRjoKgV+MG9Wr0mmPHfqpKec= Received: from mail-vk1-f197.google.com (mail-vk1-f197.google.com [209.85.221.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-65-mkLucP0EO62d6dcvG0J0Bw-1; Wed, 06 May 2020 05:36:00 -0400 X-MC-Unique: mkLucP0EO62d6dcvG0J0Bw-1 Received: by mail-vk1-f197.google.com with SMTP id x128so350504vkd.9 for ; Wed, 06 May 2020 02:36:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9v6/V4YwiDHeLyHFa30++zTN8KwR8CDu6OZlEQ2ayWw=; b=q8bOiybvvnyePcwchEBt9Gn0S3HZ0I3vnY/cm6W82ZbcVprQ+ophSwNg7/vgPUWQtr UoDy8DC8JS/Z49Z/s47nBgEyEWazCvD2nHP7adtfzhbMIgQHZsnhET0gaWANnxLnu7sk y0GE3WHJjVeDXpMxBXIMeA9jxisyHivWTZ7eJYP9SShpELMvAA4nzr+J9cdKi5THPggB OBfwfPkKBiIQ4wy8qLr5QZ2qCZRAjW+5tTzHhfFAYURqzmEAeeUupJ36BXX/2s6oZaBK 08d98Jx0Vf8apnnW/5v093Hv1sSrif7NrtEHSXEEJmQg/M3x6gHkWD7N3XJiddRnNvJQ t69A== X-Gm-Message-State: AGi0Pua+MIy9MjPcBq8XN1xuWJJGIfkQbZbyQpJbQtocuxn0DVCFp1Fg 5e2C51plt/uCDJDsu/vUveoqdMQa3d3DJX2co2vcxrJdDvongt/rUBcuksSCBKRegltqty7rJGL 0vy5ELm3vYa7anmK5itU= X-Received: by 2002:a05:6102:382:: with SMTP id m2mr7166994vsq.141.1588757760422; Wed, 06 May 2020 02:36:00 -0700 (PDT) X-Google-Smtp-Source: APiQypJUYe7lm5bb+cHtR2VG3f7O7hv43NbX/Jt1B6FZS0mnQocwVEZYbGJ5dF7qGknap3aB3OL7GiwDiKAjvYFDIB0= X-Received: by 2002:a05:6102:382:: with SMTP id m2mr7166987vsq.141.1588757760206; Wed, 06 May 2020 02:36:00 -0700 (PDT) MIME-Version: 1.0 References: <20200504174552.6700-1-drc@linux.vnet.ibm.com> <20200504210347.24094-1-drc@linux.vnet.ibm.com> <18ecc473-3d80-a232-963f-19e34c021e72@intel.com> <8f6efd02-741d-b606-3749-cae90da3be44@linux.vnet.ibm.com> In-Reply-To: From: David Marchand Date: Wed, 6 May 2020 11:35:48 +0200 Message-ID: To: David Christensen Cc: Ferruh Yigit , dev , =?UTF-8?Q?Micha=C5=82_Krawczyk?= , Marcin Wojtas , "Tzalik, Guy" , Evgeny Schemeilin , Igor Chauskin , Andrew Rybchenko X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [PATCH v2] eal: fix rte_memcpy build on ppc with gcc 9.3 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, May 5, 2020 at 10:28 PM David Christensen wrote: > > > >> The rte_altivec.h is related to another open patch required to build o= n > >> 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 t= he > >> 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=3Dc11 > 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. --=20 David Marchand