From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Alok Prasad <palok@marvell.com>, Jerin Jacob <jerinj@marvell.com>,
Olivier Matz <olivier.matz@6wind.com>,
Edwin Brossette <edwin.brossette@6wind.com>,
stable@dpdk.org
Subject: Re: [V2] net/qede: reduce the optimization level for gcc > 11
Date: Tue, 9 Sep 2025 07:27:56 +0200 [thread overview]
Message-ID: <90baf334-0c66-42f1-a4dc-0aa74e1ed6bd@6wind.com> (raw)
In-Reply-To: <20250908125913.7deb6fe6@hermes.local>
On 9/8/25 21:59, Stephen Hemminger wrote:
> On Mon, 8 Sep 2025 09:04:13 +0200
> Thierry Herbelot <thierry.herbelot@6wind.com> wrote:
>
>> +# no packet Rx with gcc > 11 with compiling with default -O3 or -O2
>> +if (cc.get_id() == 'gcc' and cc.version().version_compare('>11.0'))
>> + base_cflags += '-O1'
>> +endif
>
> Did you test with Gcc 14 and 15, it may be the bug is already fixed.
As said in the commit log:
"The same issue is also seen with gcc-12 and gcc-14."
I did not test with gcc-15.
The issue is not seen with clang20 (qede PMD compiled with -O3 works as
expected).
Best regards
Thierry
--
Thierry Herbelot
CSE - Titulaire au collège Cadres
Senior Software Engineer
http://www.6wind.com/
Follow us:
https://www.linkedin.com/company/6wind/
https://twitter.com/6WINDsoftware
https://www.youtube.com/user/6windsoftware
next prev parent reply other threads:[~2025-09-09 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:32 [PATCH] net/qede: reduce the optimization level Thierry Herbelot
2025-09-06 3:59 ` Stephen Hemminger
2025-09-08 7:04 ` [V2] net/qede: reduce the optimization level for gcc > 11 Thierry Herbelot
2025-09-08 19:59 ` Stephen Hemminger
2025-09-09 5:27 ` Thierry Herbelot [this message]
2025-09-09 5:40 ` [V3] " Thierry Herbelot
2025-09-09 16:17 ` 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=90baf334-0c66-42f1-a4dc-0aa74e1ed6bd@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=edwin.brossette@6wind.com \
--cc=jerinj@marvell.com \
--cc=olivier.matz@6wind.com \
--cc=palok@marvell.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).