DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	shperetz@nvidia.com, Ori Kam <orika@nvidia.com>
Subject: [PATCH v2 3/3] examples/flow_filtering: fix gcc 15 overflow warning
Date: Mon, 20 Jan 2025 15:23:40 -0800	[thread overview]
Message-ID: <20250120232442.505866-4-stephen@networkplumber.org> (raw)
In-Reply-To: <20250120232442.505866-1-stephen@networkplumber.org>

Gcc 15 no longer allows initialization of arrays with strings
because the null character is dropped. Resolve by using an
array initializer.

../examples/flow_filtering/snippets/snippet_match_mpls.c: In function ‘snippet_mpls_create_pattern_template’:
../examples/flow_filtering/snippets/snippet_match_mpls.c:62:31: warning: initializer-string for array of ‘unsigned char’ is too long [-Wunterminated-string-initialization]
   62 |                 .label_tc_s = "\xff\xff\xf1",
      |                               ^~~~~~~~~~~~~~

Fixes: 16158f349000 ("examples/flow_filtering: introduce use cases snippets")
Cc: shperetz@nvidia.com

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 examples/flow_filtering/snippets/snippet_match_mpls.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/examples/flow_filtering/snippets/snippet_match_mpls.c b/examples/flow_filtering/snippets/snippet_match_mpls.c
index a2e429f686..8382ec7041 100644
--- a/examples/flow_filtering/snippets/snippet_match_mpls.c
+++ b/examples/flow_filtering/snippets/snippet_match_mpls.c
@@ -59,7 +59,7 @@ snippet_mpls_create_pattern_template(uint16_t port_id, struct rte_flow_error *er
 		 * the Traffic Class set to 0,
 		 * and the Bottom of Stack bit set to 1.
 		 */
-		.label_tc_s = "\xff\xff\xf1",
+		.label_tc_s = { 0xff, 0xff, 0xf1 },
 	};
 
 	/* Define the flow pattern template. */
-- 
2.45.2


  parent reply	other threads:[~2025-01-20 23:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250110170603.538756-1-stephen@networkplumber.or>
2025-01-20 23:23 ` [PATCH v2 0/3] Fix warnings when using gcc 15 Stephen Hemminger
2025-01-20 23:23   ` [PATCH v2 1/3] crypto/cnxk: fix gcc 15 warning Stephen Hemminger
2025-01-20 23:23   ` [PATCH v2 2/3] net/thunderx/base: fix build with Gcc 15 Stephen Hemminger
2025-01-20 23:23   ` Stephen Hemminger [this message]
2025-01-22 10:50   ` [PATCH v2 0/3] Fix warnings when using gcc 15 David Marchand
2025-01-23 16:28 ` [PATCH v3 00/15] Add attributes to allocation functions Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 01/15] fib: add allocation function attributes Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 02/15] rib: annotate rib allocation functions Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 03/15] hash: add allocation function attributes Stephen Hemminger
2025-01-24  8:37     ` Konstantin Ananyev
2025-01-23 16:28   ` [PATCH v3 04/15] lpm: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 05/15] pipeline: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 06/15] acl: " Stephen Hemminger
2025-01-24  8:36     ` Konstantin Ananyev
2025-01-23 16:28   ` [PATCH v3 07/15] bitratestats: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 08/15] member: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 09/15] mempool: " Stephen Hemminger
2025-01-24  8:32     ` Konstantin Ananyev
2025-01-23 16:28   ` [PATCH v3 10/15] eventdev: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 11/15] ring: " Stephen Hemminger
2025-01-24  8:31     ` Konstantin Ananyev
2025-01-23 16:28   ` [PATCH v3 12/15] reorder: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 13/15] compressdev: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 14/15] telemetry: " Stephen Hemminger
2025-01-23 16:28   ` [PATCH v3 15/15] sched: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 00/16] Add " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 01/16] fib: add " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 02/16] rib: annotate rib allocation functions Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 03/16] hash: add allocation function attributes Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 04/16] lpm: " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 05/16] pipeline: " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 06/16] acl: " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 07/16] bitratestats: " Stephen Hemminger
2025-01-24 18:14   ` [PATCH v4 08/16] member: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 09/16] mempool: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 10/16] eventdev: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 11/16] ring: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 12/16] reorder: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 13/16] compressdev: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 14/16] telemetry: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 15/16] sched: " Stephen Hemminger
2025-01-24 18:15   ` [PATCH v4 16/16] doc: add release note about allocation attributes Stephen Hemminger

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=20250120232442.505866-4-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=shperetz@nvidia.com \
    /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).