DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and Linux
Date: Tue,  8 Jul 2014 00:36:53 +0100	[thread overview]
Message-ID: <1404776219-6130-1-git-send-email-bruce.richardson@intel.com> (raw)

This patch set enables clang compilation on FreeBSD and Linux. It includes
patches to fix a number of compilation errors thrown up by clang, and then
adds in the appropriate toolchain makefiles and compile-time configurations.

This set has been tested with clang v3.3 on FreeBSD 10 and clang v3.4 on
Fedora linux 20. The example apps folder has not been tested at this time, this
patch set only focuses on the core libraries and apps.

Bruce Richardson (6):
  pmd_bond: add missing variable initialization
  Makefiles: add clang to compiler if/else block
  mk: Ensure correct detection of SSE4.2 on FreeBSD
  acl: add nmmintrin.h header to allow clang compilation
  mk: add toolchain for clang and linuxapp target
  config: add compile target for clang on BSD

 config/defconfig_x86_64-native-bsdapp-clang   | 71 ++++++++++++++++++++++++
 config/defconfig_x86_64-native-linuxapp-clang | 63 ++++++++++++++++++++++
 lib/librte_acl/acl_bld.c                      |  1 +
 lib/librte_pmd_bond/rte_eth_bond_pmd.c        |  2 +-
 lib/librte_pmd_i40e/Makefile                  |  9 ++++
 lib/librte_pmd_ixgbe/Makefile                 |  7 +++
 lib/librte_pmd_vmxnet3/Makefile               |  7 +++
 mk/machine/native/rte.vars.mk                 | 12 +++++
 mk/toolchain/clang/rte.toolchain-compat.mk    | 43 +++++++++++++++
 mk/toolchain/clang/rte.vars.mk                | 77 +++++++++++++++++++++++++++
 10 files changed, 291 insertions(+), 1 deletion(-)
 create mode 100644 config/defconfig_x86_64-native-bsdapp-clang
 create mode 100644 config/defconfig_x86_64-native-linuxapp-clang
 create mode 100644 mk/toolchain/clang/rte.toolchain-compat.mk
 create mode 100644 mk/toolchain/clang/rte.vars.mk

-- 
1.9.3

             reply	other threads:[~2014-07-07 23:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 23:36 Bruce Richardson [this message]
2014-07-07 23:36 ` [dpdk-dev] [PATCH 1/6] pmd_bond: add missing variable initialization Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 2/6] Makefiles: add clang to compiler if/else block Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 3/6] mk: Ensure correct detection of SSE4.2 on FreeBSD Bruce Richardson
2014-07-17  9:35   ` Thomas Monjalon
2014-07-17 21:42     ` Bruce Richardson
2014-07-17 10:25   ` Thomas Monjalon
2014-07-17 14:41     ` Richardson, Bruce
2014-07-17 21:47   ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 4/6] acl: add nmmintrin.h header to allow clang compilation Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 5/6] mk: add toolchain for clang and linuxapp target Bruce Richardson
2014-07-17 10:23   ` Thomas Monjalon
2014-07-17 17:54     ` Richardson, Bruce
2014-07-07 23:36 ` [dpdk-dev] [PATCH 6/6] config: add compile target for clang on BSD Bruce Richardson
2014-07-11  5:31 ` [dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and Linux Zhan, Zhaochen
2014-07-18 23:58 ` 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=1404776219-6130-1-git-send-email-bruce.richardson@intel.com \
    --to=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 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).