From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v2] Clang compile error with RTE_LIBRTE_MEMPOOL_DEBUG enabled.
Date: Sun, 28 Sep 2014 05:30:43 +0000 [thread overview]
Message-ID: <3EC8A7DC-C947-40DC-B8FD-60023A12B00A@windriver.com> (raw)
In-Reply-To: <41114A6E-08AB-4269-9E4F-9930BD04D8E2@windriver.com>
When enabling RTE_LIBRTE_MEMPOOL_DEBUG and compiling with clang
compiler an error occurs, because ifdefed code now includes GCC pragmas.
GCC 4.4 is when push_options and pop_options pragma show up.
Signed-off-by: Keith Wiles <keith.wiles@windriver.com>
---
lib/librte_mempool/rte_mempool.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/librte_mempool/rte_mempool.h b/lib/librte_mempool/rte_mempool.h
index 95f19f9..558931a 100644
--- a/lib/librte_mempool/rte_mempool.h
+++ b/lib/librte_mempool/rte_mempool.h
@@ -312,7 +312,7 @@ static inline void __mempool_write_trailer_cookie(void *obj)
* - 2: just check that cookie is valid (free or allocated)
*/
#ifdef RTE_LIBRTE_MEMPOOL_DEBUG
-#ifndef __INTEL_COMPILER
+#if (__GNUC__ > 4) || ((__GNUC__ == 4) && (__GNUC_MINOR__ >= 4))
#pragma GCC push_options
#pragma GCC diagnostic ignored "-Wcast-qual"
#endif
@@ -379,7 +379,7 @@ static inline void __mempool_check_cookies(const struct rte_mempool *mp,
}
}
}
-#ifndef __INTEL_COMPILER
+#if (__GNUC__ > 4) || ((__GNUC__ == 4) && (__GNUC_MINOR__ >= 4))
#pragma GCC pop_options
#endif
#else
--
2.1.0
Keith Wiles, Principal Technologist with CTO office, Wind River mobile 972-213-5533
next prev parent reply other threads:[~2014-09-28 5:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 5:53 [dpdk-dev] [PATCH] " Wiles, Roger Keith
2014-09-28 1:08 ` Wiles, Roger Keith
2014-09-28 5:30 ` Wiles, Roger Keith [this message]
2014-10-01 12:58 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2014-10-01 14:57 ` Wiles, Roger Keith
2014-10-01 17:06 ` Wiles, Roger Keith
2014-10-01 17:11 ` [dpdk-dev] [PATCH v3] " Wiles, Roger Keith
2014-10-02 22:22 ` Wiles, Roger Keith
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=3EC8A7DC-C947-40DC-B8FD-60023A12B00A@windriver.com \
--to=keith.wiles@windriver.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).