From: "Montorsi, Francesco" <fmontorsi@empirix.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: warnings when including DPDK headers from a C++17 source file
Date: Sun, 15 Jul 2018 13:00:16 +0000 [thread overview]
Message-ID: <1531659613771.95891@empirix.com> (raw)
In-Reply-To: <20180713085205.1a255bf3@xeon-e3>
Hi,
________________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Friday, July 13, 2018 5:52 PM
To: Montorsi, Francesco
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] warnings when including DPDK headers from a C++17 source file
> Why is DPDK code using register keyword at all? It is ignored by modern compilers.
that's my question as well :)
Maybe register keyword could be removed at least from header files to make the life easier to whoever is using C++17... right now I worked around that by placing -Werror -Wno-register, but that's perhaps not the best solution
Francesco
prev parent reply other threads:[~2018-07-15 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:51 warnings when including DPDK headers from a C++17 source file Montorsi, Francesco
2018-07-13 15:52 ` Stephen Hemminger
2018-07-15 13:00 ` Montorsi, Francesco [this message]
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=1531659613771.95891@empirix.com \
--to=fmontorsi@empirix.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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.