On Fri, May 03, 2019 at 03:57:20AM +, Honnappa Nagarahalli wrote:
> > > On May 1, 2019, at 9:13 PM, Honnappa Nagarahalli
> > wrote:
> > >
> > >> Per armv8 crypto extension support, make build always enable it by
> > >> default as long as compiler supports the feature while meson build
> > >> o
> > On May 1, 2019, at 9:13 PM, Honnappa Nagarahalli
> wrote:
> >
> >> Per armv8 crypto extension support, make build always enable it by
> >> default as long as compiler supports the feature while meson build
> >> only enables it for 'default' machine of generic armv8 architecture.
> >> For examp
ula
> ; Gavin Hu (Arm Technology China)
> ; nd
> Subject: Re: [dpdk-dev] [PATCH 1/2] build: add option for armv8 crypto
> extension
>
> > On May 1, 2019, at 9:13 PM, Honnappa Nagarahalli
> wrote:
> >
> >> Per armv8 crypto extension support, make build alway
> On May 1, 2019, at 9:13 PM, Honnappa Nagarahalli
> wrote:
>
>> Per armv8 crypto extension support, make build always enable it by default
>> as long as compiler supports the feature while meson build only enables it
>> for
>> 'default' machine of generic armv8 architecture. For example, speci
> Per armv8 crypto extension support, make build always enable it by default
> as long as compiler supports the feature while meson build only enables it for
> 'default' machine of generic armv8 architecture. For example, specifying '-
> mcpu=cortex-a72' doesn't enable it but '+crypto' is required
Per armv8 crypto extension support, make build always enable it by default
as long as compiler supports the feature while meson build only enables it
for 'default' machine of generic armv8 architecture. For example,
specifying '-mcpu=cortex-a72' doesn't enable it but '+crypto' is required
in order
6 matches
Mail list logo
