DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 00/10] fix compilation with -Og
Date: Fri, 6 Oct 2017 01:26:17 +0100	[thread overview]
Message-ID: <0def7ae9-ad8e-1df8-18cd-ee4e9515d621@intel.com> (raw)
In-Reply-To: <20170911151333.5727-1-olivier.matz@6wind.com>

On 9/11/2017 4:13 PM, Olivier Matz wrote:
> In developer mode (RTE_DEVEL_BUILD=y) where -Werror is passed in the
> CFLAGS, the compilation fails with gcc-6.3.0 and EXTRA_CFLAGS=-Og. Some
> errors are real bugs (but not critical), while some are false positives
> (gcc bugs?).
> 
> The solution often consists in initializing a local variable to
> ensure the compiler won't complain.
> 
> The patchset contains all the fixes needed to properly compile with -Og.
> Feedback is welcome to decide if:
> 1/ we include all of them, even if some are workarounds for
>    gcc bugs
> 2/ we only include the real fixes, without fixing the compilation with
>    -Og.
> 
> 
> Olivier Matz (10):
>   net/bnxt: fix compilation with -Og
>   net/qede: fix compilation with -Og
>   net/virtio: fix compilation with -Og
>   net/i40e: fix compilation with -Og
>   uio: fix compilation with -Og
>   cmdline: fix compilation with -Og
>   metrics: fix compilation with -Og
>   lpm6: fix compilation with -Og
>   app/test-crypto-perf: fix memory leak
>   app/test-crypto-perf: fix compilation with -Og

Series applied to dpdk-next-net/master, thanks.

Except 3/10, 4/10, 8/10. Normally we don't get partial sets, that makes
life harder for everyone, but since mentioned ones requires some more
input I didn't want to make rest wait.

When those three concluded would you mind sending another set for them?

  parent reply	other threads:[~2017-10-06  0:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 15:13 Olivier Matz
2017-09-11 15:13 ` [dpdk-dev] [PATCH 01/10] net/bnxt: " Olivier Matz
2017-09-11 15:13 ` [dpdk-dev] [PATCH 02/10] net/qede: " Olivier Matz
2017-09-11 18:22   ` Patil, Harish
2017-09-11 15:13 ` [dpdk-dev] [PATCH 03/10] net/virtio: " Olivier Matz
2017-10-05 23:17   ` Ferruh Yigit
2017-10-05 23:28     ` Ferruh Yigit
2017-10-06  6:43   ` Maxime Coquelin
2017-10-06 18:43     ` Ferruh Yigit
2017-09-11 15:13 ` [dpdk-dev] [PATCH 04/10] net/i40e: " Olivier Matz
2017-10-05 23:24   ` Ferruh Yigit
2017-10-11  6:20     ` Wu, Jingjing
2017-10-11  7:52       ` Olivier MATZ
2017-09-11 15:13 ` [dpdk-dev] [PATCH 05/10] uio: " Olivier Matz
2017-09-11 15:13 ` [dpdk-dev] [PATCH 06/10] cmdline: " Olivier Matz
2017-09-11 15:13 ` [dpdk-dev] [PATCH 07/10] metrics: " Olivier Matz
2017-09-11 15:13 ` [dpdk-dev] [PATCH 08/10] lpm6: " Olivier Matz
2017-10-06  0:18   ` Ferruh Yigit
2017-10-26 10:42     ` Bruce Richardson
2017-10-26 18:54   ` Ferruh Yigit
2017-09-11 15:13 ` [dpdk-dev] [PATCH 09/10] app/test-crypto-perf: fix memory leak Olivier Matz
2017-10-05  9:29   ` De Lara Guarch, Pablo
2017-09-11 15:13 ` [dpdk-dev] [PATCH 10/10] app/test-crypto-perf: fix compilation with -Og Olivier Matz
2017-10-05  9:36   ` De Lara Guarch, Pablo
2017-09-11 15:28 ` [dpdk-dev] [PATCH 00/10] " Bruce Richardson
2017-10-06  0:26 ` Ferruh Yigit [this message]
2017-10-06  7:31   ` Olivier MATZ

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=0def7ae9-ad8e-1df8-18cd-ee4e9515d621@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).