patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <>
To: David Marchand <>,
	Aman Singh <>
Cc: dev <>, dpdk stable <>,
	Qi Zhang <>,
	Beilei Xing <>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/ice/base: fix build error for GCC 4.8.5
Date: Tue, 5 Oct 2021 15:19:26 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On 10/5/2021 2:57 PM, David Marchand wrote:
> On Tue, Oct 5, 2021 at 2:07 PM Aman Singh <> wrote:
>> Code changes done for build issue as reported in Bug 817
>> error: dereferencing type-punned pointer will break strict-aliasing rules.
>> added union to avoid pointer dereferencing
> About the title, Ali reproduced the issue with other versions of gcc.
> This patch touches base/ code, is Intel ok with this?
> Else, we could consider disabling strict aliasing for the base driver, like
> $ git grep alias '**/base/'
> drivers/net/fm10k/base/    '-Wno-strict-aliasing',
> '-Wno-format-extra-args',
> drivers/net/i40e/base/        '-Wno-strict-aliasing',
> '-Wno-unused-but-set-variable',
> drivers/net/qede/base/        '-Wno-strict-aliasing',

It has some complications to update the shared code from the DPDK, but for this
case the fix seems simple and valid, so I am for getting the fix and work on to
propagate the fix to the shared code, instead of disable the warning directly.

Mainly Qi and Beilei will be managing the shared code part, if shared code
comes with different solution, we can send an incremental patch to replace
this fix.

Briefly I am for getting the patch, hence:
Acked-by: Ferruh Yigit <>

> Bugzilla ID: 817
>> Fixes: 39925373a333 ("net/ice/base: add parser execution main loop")
> No Cc: stable, this is a regression in main.
>> Signed-off-by: Aman Singh <>
> Tested-by: David Marchand <>

      reply	other threads:[~2021-10-05 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 11:57 [dpdk-stable] " Aman Singh
2021-10-05 13:57 ` [dpdk-stable] [dpdk-dev] " David Marchand
2021-10-05 14:19   ` Ferruh Yigit [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ \
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone