> > 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.
> >
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 gc
> 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
Please check the CI results, there are some failures.
29/10/2024 02:59, Wathsala Vithanage:
> Arm recommends using -mcpu over -march and march-extensions when the
> compiler supports the target CPU (neoverse-n1 etc.). Arm build so far
> has been an amalgam of -mcpu and -march. When march is in us
Arm recommends using -mcpu over -march and march-extensions when the
compiler supports the target CPU (neoverse-n1 etc.). Arm build so far
has been an amalgam of -mcpu and -march. When march is in use, it has
been the case so far to silently fall back to a downgraded march when
the compiler does no
5 matches
Mail list logo