From: Thomas Monjalon <thomas@monjalon.net>
To: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Dhruv Tripathi <Dhruv.Tripathi@arm.com>, nd <nd@arm.com>
Subject: Re: [PATCH v2 1/2] config/arm: strict use of -mcpu for supported CPUs
Date: Mon, 11 Nov 2024 19:14:50 +0100 [thread overview]
Message-ID: <9980642.tM3a2QDmDi@thomas> (raw)
In-Reply-To: <PAWPR08MB8909AB1D0D5731610D449F0A9F582@PAWPR08MB8909.eurprd08.prod.outlook.com>
11/11/2024 18:57, Wathsala Wathawana Vithanage:
>
> > Subject: Re: [PATCH v2 1/2] config/arm: strict use of -mcpu for supported
> > CPUs
> >
> > Please check the CI results, there are some failures.
> >
>
> Hi Thomas,
>
> CI is failing because gcc version 11 does not enable crypto extension for thunderx2,
> with -mcpu=thunderx2t99 unless +crypto feature modifier is used.
> Goal of this patch is to drop use of such feature modifiers when an -mcpu is available
> for a given platform.
> This issue is fixed in gcc version 13 for thunderx2t99.
We cannot afford dropping the support of GCC 11.
Which solution do you propose?
next prev parent reply other threads:[~2024-11-11 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 23:31 [PATCH " Wathsala Vithanage
2024-10-28 23:31 ` [PATCH 2/2] config/arm: sort SOCs alphabetically Wathsala Vithanage
2024-10-29 1:06 ` [PATCH 1/2] config/arm: strict use of -mcpu for supported CPUs fengchengwen
2024-10-29 1:59 ` [PATCH v2 " Wathsala Vithanage
2024-10-29 1:59 ` [PATCH v2 2/2] config/arm: sort SOCs alphabetically Wathsala Vithanage
2024-11-11 14:12 ` [PATCH v2 1/2] config/arm: strict use of -mcpu for supported CPUs Thomas Monjalon
2024-11-11 17:57 ` Wathsala Wathawana Vithanage
2024-11-11 18:14 ` Thomas Monjalon [this message]
2024-11-11 19:46 ` Wathsala Wathawana Vithanage
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=9980642.tM3a2QDmDi@thomas \
--to=thomas@monjalon.net \
--cc=Dhruv.Tripathi@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=wathsala.vithanage@arm.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).