From: "Simon Kågström" <simon.kagstrom@netinsight.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] headers: typeof -> __typeof__ to unbreak C++11 code
Date: Thu, 26 Feb 2015 12:24:33 +0100 [thread overview]
Message-ID: <54EF0271.8070508@netinsight.net> (raw)
In-Reply-To: <1976981.gNbPL03jx1@xps13>
On 2015-02-26 12:14, Thomas Monjalon wrote:
> 2015-02-25 14:28, Simon Kagstrom:
>> When compiling C++11-code or above (--std=c++11), the build fails with
>> lots of
>>
>> rte_eth_ctrl.h:517:3: note: in expansion of macro RTE_ALIGN
>> (RTE_ALIGN(RTE_ETH_FLOW_MAX, UINT32_BIT)/UINT32_BIT)
>> ^
> I'd like to be sure that it's working with every compilers we support
> (gcc, icc, clang).
> Anyone to check please?
I guess you mean compiling DPDK itself, but I can add that compiling my
example "app" (i.e., a file which includes the DPDK headers and an empty
main()) with clang++ gives more problems:
include/rte_devargs.h:89:5: error:
'virtual' can only appear on non-static member functions
} virtual;
^
and a slew of warnings of the type
include/rte_byteorder_64.h:45:2: warning:
'register' storage class specifier is deprecated
[-Wdeprecated-register]
register uint64_t x = _x;
^~~~~~~~~
include/rte_memcpy.h:85:25: warning:
cast from 'const uint8_t *' (aka 'const unsigned char *') to
'const __m128i *' increases required alignment from 1 to 16
[-Wcast-align]
xmm0 = _mm_loadu_si128((const __m128i *)src);
// Simon
next prev parent reply other threads:[~2015-02-26 11:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 13:28 Simon Kagstrom
2015-02-26 11:14 ` Thomas Monjalon
2015-02-26 11:24 ` Simon Kågström [this message]
2015-02-26 16:02 ` Mcnamara, John
2015-02-27 16:24 ` Ananyev, Konstantin
2015-03-02 7:55 ` Simon Kågström
2015-03-06 8:28 ` Simon Kågström
2015-03-06 10:30 ` Ananyev, Konstantin
2015-03-06 13:42 ` Simon Kågström
2015-03-06 15:59 ` [dpdk-dev] [PATCHv2] " Konstantin Ananyev
2015-03-09 16:38 ` 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=54EF0271.8070508@netinsight.net \
--to=simon.kagstrom@netinsight.net \
--cc=dev@dpdk.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).