From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, thomas@monjalon.net
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: add function name to log message
Date: Fri, 12 Oct 2018 11:42:03 +0100 [thread overview]
Message-ID: <98717fc3-c3dd-cc4f-e5ff-b5310e47d6ee@intel.com> (raw)
In-Reply-To: <20181011175940.6800-1-stephen@networkplumber.org>
On 10/11/2018 6:59 PM, Stephen Hemminger wrote:
> @@ -161,8 +161,9 @@ extern "C" {
>
> extern int rte_eth_dev_logtype;
>
> -#define RTE_ETHDEV_LOG(level, ...) \
> - rte_log(RTE_LOG_ ## level, rte_eth_dev_logtype, "" __VA_ARGS__)
> +#define RTE_ETHDEV_LOG(level, fmt, ...) \
> + rte_log(RTE_LOG_ ## level, rte_eth_dev_logtype, \
> + "%s():" fmt, __func__, ## __VA_ARGS__)
+1 to adding function name, but
failsafe is giving build error [1] with clang because of ## usage [2], that is
why I add this as ` "" __VA_ARGS__` at first place but you can't do this trick
if __VA_ARGS__ used after fmt.
I am not aware of a solution for this, __VA_OPT__(,) also didn't worked with clang.
[1]
.../build/include/rte_ethdev.h:166:26: error: token pasting of ',' and
__VA_ARGS__ is a GNU extension [-Werror,-Wgnu-zero-variadic-macro-arguments]
"%s():" fmt, __func__, ## __VA_ARGS__)
^
[2]
This seems because of "-pedantic" argument driver uses, and other PMDs using
"-pedantic", like mlx, will have same error although they are disable by
default and error not observed in default build.
next prev parent reply other threads:[~2018-10-12 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 17:59 Stephen Hemminger
2018-10-12 10:42 ` Ferruh Yigit [this message]
2018-10-12 10:45 ` Ferruh Yigit
2018-10-12 12:43 ` Adrien Mazarguil
2018-10-12 14:54 ` Stephen Hemminger
2018-10-16 15:55 ` Ferruh Yigit
2018-10-17 9:26 ` Gaëtan Rivet
2018-10-17 17:08 ` Ferruh Yigit
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=98717fc3-c3dd-cc4f-e5ff-b5310e47d6ee@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).