From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
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>,
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:46:08 +0000 [thread overview]
Message-ID: <PAWPR08MB8909EC07D26269AA13D0FA639F582@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <9980642.tM3a2QDmDi@thomas>
> > 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?
>
Adding a pseudo mcpu for thunderx2t99 as described in the patch. I will send a v3
with that change.
prev parent reply other threads:[~2024-11-11 19:46 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
2024-11-11 19:46 ` Wathsala Wathawana Vithanage [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:
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=PAWPR08MB8909EC07D26269AA13D0FA639F582@PAWPR08MB8909.eurprd08.prod.outlook.com \
--to=wathsala.vithanage@arm.com \
--cc=Dhruv.Tripathi@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--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).