From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org,
Simon Kagstrom
<simon.kagstrom-vI6UBbBVNY+JA8cjQkG2/g@public.gmane.org>
Subject: Re: [PATCH] headers: typeof -> __typeof__ to unbreak C++11 code
Date: Thu, 26 Feb 2015 12:14:39 +0100 [thread overview]
Message-ID: <1976981.gNbPL03jx1@xps13> (raw)
In-Reply-To: <20150225142851.55406347@miho>
Hi Simon,
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)
> ^
>
> When reading the GCC info pages, I get the feeling that __typeof__ is
> a better choice, and that indeed works when including the headers in
> C++ files (--std=c++11).
I'd like to be sure that it's working with every compilers we support
(gcc, icc, clang).
Anyone to check please?
next prev parent reply other threads:[~2015-02-26 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 13:28 [PATCH] headers: typeof -> __typeof__ to unbreak C++11 code Simon Kagstrom
2015-02-26 11:14 ` Thomas Monjalon [this message]
2015-02-26 11:24 ` Simon Kågström
2015-02-26 16:02 ` Mcnamara, John
2015-02-27 16:24 ` Ananyev, Konstantin
[not found] ` <2601191342CEEE43887BDE71AB977258213F3012-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-03-02 7:55 ` Simon Kågström
[not found] ` <54F41765.1050403-vI6UBbBVNY+JA8cjQkG2/g@public.gmane.org>
2015-03-06 8:28 ` Simon Kågström
[not found] ` <54F9651B.7060603-vI6UBbBVNY+JA8cjQkG2/g@public.gmane.org>
2015-03-06 10:30 ` Ananyev, Konstantin
[not found] ` <2601191342CEEE43887BDE71AB977258213F44D4-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-03-06 13:42 ` Simon Kågström
2015-03-06 15:59 ` [PATCHv2] " Konstantin Ananyev
[not found] ` <1425657587-23516-1-git-send-email-konstantin.ananyev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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=1976981.gNbPL03jx1@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=simon.kagstrom-vI6UBbBVNY+JA8cjQkG2/g@public.gmane.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.