DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andy Green <andy@warmcat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/2] ring: fix declaration after code
Date: Mon, 28 May 2018 10:29:05 +0800	[thread overview]
Message-ID: <152747454575.35192.11685010940587705005.stgit@localhost.localdomain> (raw)
In-Reply-To: <152747443129.35192.15673273827095899997.stgit@localhost.localdomain>

On gcc 5.4.0 / native aarch64 from Ubuntu 16.04:

/home/agreen/lagopus/src/dpdk/build/include/
rte_ring_c11_mem.h: In function
'__rte_ring_move_prod_head':
/home/agreen/lagopus/src/dpdk/build/include/
rte_ring_c11_mem.h:69:3: warning: ISO C90
forbids mixed declarations and code
[-Wdeclaration-after-statement]
   const uint32_t cons_tail = r->cons.tail;
   ^
/home/agreen/lagopus/src/dpdk/build/include/
rte_ring_c11_mem.h: In function
'__rte_ring_move_cons_head':
/home/agreen/lagopus/src/dpdk/build/include/
rte_ring_c11_mem.h:136:3: warning: ISO C90
forbids mixed declarations and code
[-Wdeclaration-after-statement]
   const uint32_t prod_tail = r->prod.tail;
   ^

Signed-off-by: Andy Green <andy@warmcat.com>
Fixes: 39368ebfc6 ("ring: introduce C11 memory model barrier option")
---
 lib/librte_ring/rte_ring_c11_mem.h |    8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/lib/librte_ring/rte_ring_c11_mem.h b/lib/librte_ring/rte_ring_c11_mem.h
index cb3f82b1a..3cc339558 100644
--- a/lib/librte_ring/rte_ring_c11_mem.h
+++ b/lib/librte_ring/rte_ring_c11_mem.h
@@ -61,12 +61,14 @@ __rte_ring_move_prod_head(struct rte_ring *r, unsigned int is_sp,
 	int success;
 
 	do {
+		const uint32_t cons_tail = r->cons.tail;
+
 		/* Reset n to the initial burst count */
 		n = max;
 
 		*old_head = __atomic_load_n(&r->prod.head,
 					__ATOMIC_ACQUIRE);
-		const uint32_t cons_tail = r->cons.tail;
+
 		/*
 		 *  The subtraction is done between two unsigned 32bits value
 		 * (the result is always modulo 32 bits even if we have
@@ -129,11 +131,13 @@ __rte_ring_move_cons_head(struct rte_ring *r, int is_sc,
 
 	/* move cons.head atomically */
 	do {
+		const uint32_t prod_tail = r->prod.tail;
+
 		/* Restore n as it may change every loop */
 		n = max;
 		*old_head = __atomic_load_n(&r->cons.head,
 					__ATOMIC_ACQUIRE);
-		const uint32_t prod_tail = r->prod.tail;
+
 		/* The subtraction is done between two unsigned 32bits value
 		 * (the result is always modulo 32 bits even if we have
 		 * cons_head > prod_tail). So 'entries' is always between 0

  reply	other threads:[~2018-05-28  2:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28  2:29 [dpdk-dev] [PATCH 0/2] dpdk header fixes for aarch64 Andy Green
2018-05-28  2:29 ` Andy Green [this message]
2018-05-28  8:15   ` [dpdk-dev] [PATCH 1/2] ring: fix declaration after code Gavin Hu
2018-05-28  8:46     ` Andy Green
2018-05-28  8:54       ` Gavin Hu
2018-05-28  2:29 ` [dpdk-dev] [PATCH 2/2] ring: fix sign conversion warning Andy Green
2018-05-28  9:03 ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 Andy Green
2018-05-28  9:03   ` [dpdk-dev] [PATCH v2 1/2] ring: fix declaration after code Andy Green
2018-07-16  7:15     ` Olivier Matz
2018-05-28  9:03   ` [dpdk-dev] [PATCH v2 2/2] ring: fix sign conversion warning Andy Green
2018-07-16  7:16     ` Olivier Matz
2018-07-26 13:30   ` [dpdk-dev] [PATCH v2 0/2] dpdk header fixes for aarch64 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=152747454575.35192.11685010940587705005.stgit@localhost.localdomain \
    --to=andy@warmcat.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).