All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Hu <Gavin.Hu@arm.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v5 1/2] mk: fix cross build errors
Date: Wed, 30 May 2018 10:32:24 +0200	[thread overview]
Message-ID: <3248809.BvU3dfXijd@xps> (raw)
In-Reply-To: <VI1PR08MB316752A4CB8ADB1E2AF5CA958F6C0@VI1PR08MB3167.eurprd08.prod.outlook.com>

30/05/2018 04:45, Gavin Hu:
> From: Bruce Richardson <bruce.richardson@intel.com>
> > On Tue, May 29, 2018 at 04:45:55PM +0200, Thomas Monjalon wrote:
> > > 28/05/2018 15:24, Bruce Richardson:
> > > > Would a simpler solution for this not be to put "-Wno-implicit-
> > fallthrough"
> > > > for pmdinfogen? GCC will not give a warning for an unrecognised "-Wno"
> > > > flag when compiling, unless there are other errors. This means we
> > > > can just use the flag without bothering with version checks.
> > >
> > > No, it does not work.
> > > I have this error with clang 5.0.1:
> > >     error: unknown warning option '-Wno-format-truncation'
> > >
> > Yes, you still need to check for GCC to use the flag, just not for a specific
> > version of GCC.
> >
> > /Bruce
> [Gavin Hu] Hi Thomas, '-Wno-format-truncation' is applied to gcc only, not to clang.
> Gcc, icc and clang have their own WERROR_FLAGS, they should not mix up with each other.

Now I understand what we missed from the beginning: I am testing with meson.
This flag is added unconditionnaly in config/meson.build.

> @Bruce,
> Yes, in this sense, I am really concerned about to add -Wno-implicit-fallthrough option in the pmdinfogen Makefile, as it impacts not only gcc, but also clang and icc.
> Maybe this not a best solution, as maybe it is not supported by all compilers. So should I fall back to the previous patch which check for the gcc version and apply the options for gcc only?

  reply	other threads:[~2018-05-30  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  2:45 [dpdk-stable] [PATCH v5 1/2] mk: fix cross build errors Gavin Hu
2018-05-30  8:32 ` Thomas Monjalon [this message]
2018-05-30  9:41   ` Gavin Hu
2018-05-30 10:18     ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2018-05-29  7:21 [PATCH v4 0/2] *** cross gcc fix and guide doc *** Gavin Hu
2018-05-29 10:43 ` [PATCH v5 0/2] *** cross gcc compile fix and add a " Gavin Hu
2018-05-29 10:43   ` [PATCH v5 1/2] mk: fix cross build errors Gavin Hu
2018-05-29 15:09     ` [dpdk-stable] " Thomas Monjalon

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=3248809.BvU3dfXijd@xps \
    --to=thomas@monjalon.net \
    --cc=Gavin.Hu@arm.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.