[v2] app/testpmd: fix flex item compilation error
Checks
Commit Message
When configuring meson with option "--optimization=1", gcc
complains "maybe-uninitialized" warning and it was treated as
error since Werror is enabled.
Assign fp to NULL at declaration can avoid this.
Bugzilla ID: 1163
Fixes: c8e25fbf1440 ("ethdev: add flow flex modify")
Cc: stable@dpdk.org
Reported-by: gaodaxue <daxuex.gao@intel.com>
Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
---
app/test-pmd/cmdline_flow.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
21/02/2023 11:02, Rongwei Liu:
> When configuring meson with option "--optimization=1", gcc
> complains "maybe-uninitialized" warning and it was treated as
> error since Werror is enabled.
>
> Assign fp to NULL at declaration can avoid this.
That's probably a false positive,
but I'm OK to workaround it this way, especially in a test application.
> Bugzilla ID: 1163
> Fixes: c8e25fbf1440 ("ethdev: add flow flex modify")
> Cc: stable@dpdk.org
>
> Reported-by: gaodaxue <daxuex.gao@intel.com>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> ---
> - struct flex_item *fp;
> + struct flex_item *fp = NULL;
Applied, thanks.
@@ -8992,7 +8992,7 @@ parse_vc_modify_field_level(struct context *ctx, const struct token *token,
unsigned int size)
{
struct rte_flow_action_modify_field *action;
- struct flex_item *fp;
+ struct flex_item *fp = NULL;
uint32_t val;
struct buffer *out = buf;
char *end;