From: Keith Wiles <keith.wiles@intel.com>
To: dev@dpdk.org
Subject: [PATCH 09/10] acl: update code to use __rte_weak macro
Date: Fri, 3 Aug 2018 09:06:04 -0500 [thread overview]
Message-ID: <20180803140605.43072-9-keith.wiles@intel.com> (raw)
In-Reply-To: <20180803140605.43072-1-keith.wiles@intel.com>
Signed-off-by: Keith Wiles <keith.wiles@intel.com>
---
lib/librte_acl/rte_acl.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/librte_acl/rte_acl.c b/lib/librte_acl/rte_acl.c
index 2f1243cde..db7d3221e 100644
--- a/lib/librte_acl/rte_acl.c
+++ b/lib/librte_acl/rte_acl.c
@@ -16,7 +16,7 @@ EAL_REGISTER_TAILQ(rte_acl_tailq)
* If the compiler doesn't support AVX2 instructions,
* then the dummy one would be used instead for AVX2 classify method.
*/
-int __attribute__ ((weak))
+__rte_weak int
rte_acl_classify_avx2(__rte_unused const struct rte_acl_ctx *ctx,
__rte_unused const uint8_t **data,
__rte_unused uint32_t *results,
@@ -26,7 +26,7 @@ rte_acl_classify_avx2(__rte_unused const struct rte_acl_ctx *ctx,
return -ENOTSUP;
}
-int __attribute__ ((weak))
+__rte_weak int
rte_acl_classify_sse(__rte_unused const struct rte_acl_ctx *ctx,
__rte_unused const uint8_t **data,
__rte_unused uint32_t *results,
@@ -36,7 +36,7 @@ rte_acl_classify_sse(__rte_unused const struct rte_acl_ctx *ctx,
return -ENOTSUP;
}
-int __attribute__ ((weak))
+__rte_weak int
rte_acl_classify_neon(__rte_unused const struct rte_acl_ctx *ctx,
__rte_unused const uint8_t **data,
__rte_unused uint32_t *results,
@@ -46,7 +46,7 @@ rte_acl_classify_neon(__rte_unused const struct rte_acl_ctx *ctx,
return -ENOTSUP;
}
-int __attribute__ ((weak))
+__rte_weak int
rte_acl_classify_altivec(__rte_unused const struct rte_acl_ctx *ctx,
__rte_unused const uint8_t **data,
__rte_unused uint32_t *results,
--
2.17.1
next prev parent reply other threads:[~2018-08-03 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 14:05 [PATCH 01/10] eal: add shorthand __rte_weak macro Keith Wiles
2018-08-03 14:05 ` [PATCH 02/10] qat: update code to use " Keith Wiles
2018-08-29 9:27 ` Jozwiak, TomaszX
2018-08-03 14:05 ` [PATCH 03/10] avf: " Keith Wiles
2018-08-03 14:05 ` [PATCH 04/10] fm10k: " Keith Wiles
2018-08-03 14:06 ` [PATCH 05/10] i40e: " Keith Wiles
2018-08-03 14:06 ` [PATCH 06/10] ixgbe: " Keith Wiles
2018-08-03 14:06 ` [PATCH 07/10] mlx5: " Keith Wiles
2018-08-03 17:32 ` Yongseok Koh
2018-08-03 14:06 ` [PATCH 08/10] virtio: " Keith Wiles
2018-08-03 14:06 ` Keith Wiles [this message]
2018-08-03 14:06 ` [PATCH 10/10] bpf: " Keith Wiles
2018-10-03 16:09 ` [PATCH 01/10] eal: add shorthand " Ferruh Yigit
2018-10-05 14:11 ` Wiles, Keith
2018-10-05 14:48 ` [PATCH v2] add shorthand support for " Keith Wiles
2018-10-24 23:59 ` Thomas Monjalon
2018-10-05 14:49 ` [PATCH 01/10] eal: add shorthand " Wiles, 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=20180803140605.43072-9-keith.wiles@intel.com \
--to=keith.wiles@intel.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 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.