From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Rasesh Mody <rasesh.mody@qlogic.com>,
dev@dpdk.org, stephen@networkplumber.org,
Ameen Rahman <ameen.rahman@qlogic.com>,
Harish Patil <harish.patil@qlogic.com>,
Sony Chacko <sony.chacko@qlogic.com>
Subject: [dpdk-dev] Compiler minimum versions. (Was: [PATCH v5 05/10] qede: Add core driver)
Date: Fri, 22 Apr 2016 11:48:51 +0100 [thread overview]
Message-ID: <20160422104851.GA6476@bricha3-MOBL3> (raw)
In-Reply-To: <2663604.CUOUCMLdhT@xps13>
On Wed, Apr 20, 2016 at 10:54:51AM +0200, Thomas Monjalon wrote:
> 2016-04-20 01:09, Rasesh Mody:
> > Hi Thomas,
> >
> > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > Sent: Tuesday, April 19, 2016 5:59 AM
> > >
> > > 2016-03-31 19:15, Rasesh Mody:
> > > > +ifeq ($(OS_TYPE),Linux)
> > > > +CFLAGS_ECORE_DRIVER += -Wno-shift-negative-value endif
> > >
> > > I see an error with clang:
> > > fatal error: unknown warning option '-Wno-shift-negative-value';
> > > did you mean '-Wno-shift-sign-overflow'?
> >
> > We had compiled all our v5 driver patches against clang v3.8 on RH7.1 and didn't see a similar error.
> > "clang version 3.8.0 (trunk 249596) (llvm/trunk 249595)"
> >
> > The '-Wno-shift-negative-value' option only got introduced after 3.6.0 clang release. Pls. let us know if we need to support a minimum version of clang. We had asked this question earlier in the dpdk community, however we didn't hear back from anyone so far.
>
> I use clang-3.6.2.
> You are right there is no official requirement in
> doc/guides/linux_gsg/sys_reqs.rst.
> Opinions about minimal version to support?
[Updating subject to make this discussion easier to find in searches]
Given that we support FreeBSD 10.x, Clang 3.4 may be a good minimum version
to support.
On the gcc side, v4.5 is rather old by now, should we update min to v4.8?
/Bruce
next prev parent reply other threads:[~2016-04-22 10:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 2:15 [dpdk-dev] [PATCH v5 00/10] qede: Add qede PMD Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 01/10] qede: Add maintainers Rasesh Mody
2016-04-18 16:41 ` Thomas Monjalon
2016-04-18 21:40 ` Harish Patil
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 02/10] qede: Add documentation Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 03/10] qede: Add license file Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 04/10] qede: Add base driver Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 05/10] qede: Add core driver Rasesh Mody
2016-04-01 15:41 ` Stephen Hemminger
2016-04-01 15:42 ` Stephen Hemminger
2016-04-19 12:35 ` Thomas Monjalon
2016-04-19 12:59 ` Thomas Monjalon
2016-04-20 1:09 ` Rasesh Mody
2016-04-20 8:54 ` Thomas Monjalon
2016-04-22 10:48 ` Bruce Richardson [this message]
2016-04-19 13:18 ` Thomas Monjalon
2016-04-20 1:10 ` Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 06/10] qede: Add L2 support Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 07/10] qede: Add SRIOV support Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 08/10] qede: Add attention support Rasesh Mody
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 09/10] qede: Add DCBX support Rasesh Mody
2016-04-19 12:51 ` Thomas Monjalon
2016-04-01 2:15 ` [dpdk-dev] [PATCH v5 10/10] qede: Enable PMD build Rasesh Mody
2016-04-18 15:34 ` Thomas Monjalon
2016-04-20 0:07 ` Harish Patil
2016-04-18 15:37 ` Thomas Monjalon
2016-04-20 0:14 ` Harish Patil
2016-04-20 8:51 ` Thomas Monjalon
2016-04-20 9:25 ` Bruce Richardson
2016-04-20 16:43 ` Harish Patil
2016-04-21 10:01 ` Bruce Richardson
2016-04-20 16:36 ` Harish Patil
2016-04-01 15:44 ` [dpdk-dev] [PATCH v5 00/10] qede: Add qede PMD Stephen Hemminger
2016-04-01 15:51 ` Harish Patil
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=20160422104851.GA6476@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=ameen.rahman@qlogic.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=rasesh.mody@qlogic.com \
--cc=sony.chacko@qlogic.com \
--cc=stephen@networkplumber.org \
--cc=thomas.monjalon@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).