On 01/17/2019 05:17 PM, Harry van Haaren wrote:
> This commit reworks the checks for binutils 2.30 and how
> the flags to disable AVX512F are passed to the compiler.
>
> Previously the #define for including AVX512 code was set,
> while the -mno-avx512f argument was given to the compiler.
> This wo
17/01/2019 18:23, Ferruh Yigit:
> On 1/17/2019 5:17 PM, Harry van Haaren wrote:
> > This commit reworks the checks for binutils 2.30 and how
> > the flags to disable AVX512F are passed to the compiler.
> >
> > Previously the #define for including AVX512 code was set,
> > while the -mno-avx512f arg
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, January 17, 2019 5:56 PM
> To: Van Haaren, Harry
> Cc: dev@dpdk.org; Yigit, Ferruh ; Richardson, Bruce
>
> Subject: Re: [dpdk-dev] [PATCH] meson: fix compilation with bi
17/01/2019 18:17, Harry van Haaren:
> +# get binutils version for the workaround of Bug 97
> +ldver = run_command('ld', '-v').stdout().strip()
> +if ldver.contains('2.30')
> + if cc.has_argument('-mno-avx512f')
> + march_opt += '-mno-avx512f'
> + message('Binutils 2.30 d
On 1/17/2019 5:17 PM, Harry van Haaren wrote:
> This commit reworks the checks for binutils 2.30 and how
> the flags to disable AVX512F are passed to the compiler.
>
> Previously the #define for including AVX512 code was set,
> while the -mno-avx512f argument was given to the compiler.
> This woul
This commit reworks the checks for binutils 2.30 and how
the flags to disable AVX512F are passed to the compiler.
Previously the #define for including AVX512 code was set,
while the -mno-avx512f argument was given to the compiler.
This would cause gcc to correctly refuse to emit AVX512
instruction
6 matches
Mail list logo
