patches for DPDK stable branches
 help / color / mirror / Atom feed
* [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then?
@ 2021-06-28  7:34 Christian Ehrhardt
  2021-06-28  9:13 ` Luca Boccassi
  0 siblings, 1 reply; 3+ messages in thread
From: Christian Ehrhardt @ 2021-06-28  7:34 UTC (permalink / raw)
  To: dpdk stable, Luca Boccassi, Kevin Traynor, Akhil Goyal

Hi,
there is an old patch [1] which back then was not considered/taken
into 19.11 series.
This is now breaking Clang build [2].

Since you were the Author/Maintainers back then I wanted to ask if
there was a reason to not pick it? If it should be picked now and if
there are any special things to consider for a backport?

Chiming in/subscribing to the bug would also be appreciated.

[1]: https://github.com/DPDK/dpdk/commit/eef9e0412a84cddf8944379ed4995314b4369370
[2]: https://bugs.dpdk.org/show_bug.cgi?id=733#c6

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then?
  2021-06-28  7:34 [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then? Christian Ehrhardt
@ 2021-06-28  9:13 ` Luca Boccassi
  2021-06-28  9:47   ` Kevin Traynor
  0 siblings, 1 reply; 3+ messages in thread
From: Luca Boccassi @ 2021-06-28  9:13 UTC (permalink / raw)
  To: Christian Ehrhardt, dpdk stable, Kevin Traynor, Akhil Goyal

On Mon, 2021-06-28 at 09:34 +0200, Christian Ehrhardt wrote:
> Hi,
> there is an old patch [1] which back then was not considered/taken
> into 19.11 series.
> This is now breaking Clang build [2].
> 
> Since you were the Author/Maintainers back then I wanted to ask if
> there was a reason to not pick it? If it should be picked now and if
> there are any special things to consider for a backport?
> 
> Chiming in/subscribing to the bug would also be appreciated.
> 
> [1]: https://github.com/DPDK/dpdk/commit/eef9e0412a84cddf8944379ed4995314b4369370
> [2]: https://bugs.dpdk.org/show_bug.cgi?id=733#c6

Can't remember the details about this particular one, but I think
several fixes were backported for the -fno-common issue in 19.11

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then?
  2021-06-28  9:13 ` Luca Boccassi
@ 2021-06-28  9:47   ` Kevin Traynor
  0 siblings, 0 replies; 3+ messages in thread
From: Kevin Traynor @ 2021-06-28  9:47 UTC (permalink / raw)
  To: Luca Boccassi, Christian Ehrhardt, dpdk stable, Akhil Goyal

On 28/06/2021 10:13, Luca Boccassi wrote:
> On Mon, 2021-06-28 at 09:34 +0200, Christian Ehrhardt wrote:
>> Hi,
>> there is an old patch [1] which back then was not considered/taken
>> into 19.11 series.
>> This is now breaking Clang build [2].
>>
>> Since you were the Author/Maintainers back then I wanted to ask if
>> there was a reason to not pick it? If it should be picked now and if
>> there are any special things to consider for a backport?
>>
>> Chiming in/subscribing to the bug would also be appreciated.
>>
>> [1]: https://github.com/DPDK/dpdk/commit/eef9e0412a84cddf8944379ed4995314b4369370
>> [2]: https://bugs.dpdk.org/show_bug.cgi?id=733#c6
> 
> Can't remember the details about this particular one, but I think
> several fixes were backported for the -fno-common issue in 19.11
> 

I have some recollection is that as -fcommon was the default in gcc at
the time of 18.11/19.11 release, using the patch 50b03f3b8eaf
("drivers/crypto: disable gcc 10 no-common errors") to continue to keep
it building in the same way, may have been seen as more acceptable in
stable than using the same patch on main when gcc had a different default.

I had to send that patch as there was no fuller solution provided by the
crypto maintainers at the time. Then, late on it was provided and
applied to main.

So it might have been a mix of the workaround seen as good enough for
stable and the other patch coming in late, but I'm not 100% about it.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-06-28  9:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-28  7:34 [dpdk-stable] Why was "drivers/crypto: fix build with -fno-common" not picked for 19.11 stable back then? Christian Ehrhardt
2021-06-28  9:13 ` Luca Boccassi
2021-06-28  9:47   ` Kevin Traynor

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 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/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git