From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v7 22/25] mlx5: work around spurious compilation errors Date: Mon, 27 Jun 2016 13:12:15 +0100 Message-ID: <20160627121215.GA15684@bricha3-MOBL3> References: <1466758261-25986-1-git-send-email-nelio.laranjeiro@6wind.com> <1466774284-20932-1-git-send-email-nelio.laranjeiro@6wind.com> <1466774284-20932-23-git-send-email-nelio.laranjeiro@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, Ferruh Yigit , Adrien Mazarguil To: Nelio Laranjeiro Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 8FF6958C5 for ; Mon, 27 Jun 2016 14:12:21 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1466774284-20932-23-git-send-email-nelio.laranjeiro@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Jun 24, 2016 at 03:18:01PM +0200, Nelio Laranjeiro wrote: > From: Adrien Mazarguil > > Since commit "mlx5: resurrect Tx gather support", older GCC versions (such > as 4.8.5) may complain about the following: > > mlx5_rxtx.c: In function `mlx5_tx_burst': > mlx5_rxtx.c:705:25: error: `wqe' may be used uninitialized in this > function [-Werror=maybe-uninitialized] > > mlx5_rxtx.c: In function `mlx5_tx_burst_inline': > mlx5_rxtx.c:864:25: error: `wqe' may be used uninitialized in this > function [-Werror=maybe-uninitialized] > > In both cases, this code cannot be reached when wqe is not initialized. > > Considering older GCC versions are still widely used, work around this > issue by initializing wqe preemptively, even if it should not be necessary. > > Signed-off-by: Adrien Mazarguil Since the previous patch is known to break the build on older compilers, I think it would be better to merge this patch into the previous to prevent the break from occurring in the first place. That will help with any future git-bisects that people run. If there is no objection, and no other issues appear requiring a new rev of this patchset, I'll merge patches 21 and 22 on apply. Regards, /Bruce