All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/mlx: fix compile errors with ignore pedantic pragma
Date: Tue, 20 Sep 2016 14:51:27 +0200	[thread overview]
Message-ID: <20160920125126.GG17252@6wind.com> (raw)
In-Reply-To: <20160919152605.GG45548@bricha3-MOBL3>

On Mon, Sep 19, 2016 at 04:26:05PM +0100, Bruce Richardson wrote:
> On Mon, Sep 19, 2016 at 04:59:59PM +0200, Adrien Mazarguil wrote:
> > Hi Bruce,
> > 
> > On Mon, Sep 19, 2016 at 03:36:54PM +0100, Bruce Richardson wrote:
> > > With recent gcc versions, e.g. gcc 6.1, compilation of mlx drivers with
> > > debug enabled produces lots of errors complaining that "pedantic" is
> > > not a warning level that can be ignored.
> > > 
> > > error: ‘-pedantic’ is not an option that controls warnings [-Werror=pragmas]
> > >  #pragma GCC diagnostic ignored "-pedantic"
> > >                                  ^~~~~~~~~~~
> > > 
> > > These errors can be removed by changing the "-pedantic" to "-Wpedantic".
> > 
> > Nice to have a workaround, I thought they did not keep the option at all.
> > However after testing:
> > 
> > - It does not seem to work with GCC 4.6 and older, they prefer -pedantic:
> >   "warning: unknown option after `#pragma GCC diagnostic' kind".
> > 
> > - GCC 4.9 (possibly 5.x as well) does not care, can use either -pedantic or
> >   -Wpedantic.
> > 
> > - GCC 6 can only supports -Wpedantic.
> > 
> > Note we're working toward removing the need for these #pragma in the first
> > place as soon as possible, however in the meantime I fear that checking the
> > GCC version is necessary.
> > 
> Depends on how old of GCC version we need to support. From the release notes
> it appears that -Wpedantic was introduced in GCC 4.8 (3 1/2 years ago).
> 
> https://gcc.gnu.org/gcc-4.8/changes.html
> 
> Do we need to support compilation on gcc versions older than this?

I'm all for upgrading so I do not really mind if we stop caring about older
GCC versions (especially considering this problem only occurs in debugging
mode which is seldom used by non-developers). The version check is necessary
if we want to keep full compatibility with at least:

- RHEL <= 6.x
- Debian <= 7.x
- Ubuntu <= 13.04

Works for me either way, thus:

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2016-09-20 12:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 14:36 [PATCH] net/mlx: fix compile errors with ignore pedantic pragma Bruce Richardson
2016-09-19 14:59 ` Adrien Mazarguil
2016-09-19 15:26   ` Bruce Richardson
2016-09-20 12:51     ` Adrien Mazarguil [this message]
2016-09-20 15:58       ` Bruce Richardson
2016-09-20 18:17         ` Adrien Mazarguil
2016-09-30 14:33           ` Ferruh Yigit
2016-09-21  5:11         ` Panu Matilainen
2016-09-21  9:48       ` Bruce Richardson

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=20160920125126.GG17252@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=bruce.richardson@intel.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 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.