DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH] meson: fix compilation with binutils version 2.30
Date: Thu, 17 Jan 2019 19:23:08 +0100	[thread overview]
Message-ID: <2654509.CpMWhpLgrV@xps> (raw)
In-Reply-To: <884f29ec-a85d-41f2-abd7-17b5bbeea3bb@intel.com>

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 argument was given to the compiler.
> > This would cause gcc to correctly refuse to emit AVX512
> > instructions, but the rte_memcpy code that includes AVX512
> > optimizations was being added to the build.
> > 
> > The check for binutils check is now moved to x86 as it is
> > irrelevant for other architectures, and the -mno-avx512f
> > flag is passed to a march_opts array in meson. As the
> > -mno-avx512 flag is added earlier in the build, the code
> > in rte_memcpy is no longer attempted to be compiled.
> > 
> > This commit also adds a message print in the meson configure
> > stage to alert the user of the workaround being employed.
> > 
> > Fixes: a32ca9a4ebc1 ("mk: fix scope of disabling AVX512F support")
> > 
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> 
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
> 
> Thanks for the fix Harry.

Applied (with message reworded as suggested), thanks

  reply	other threads:[~2019-01-17 18:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 17:17 Harry van Haaren
2019-01-17 17:23 ` Ferruh Yigit
2019-01-17 18:23   ` Thomas Monjalon [this message]
2019-01-17 17:56 ` Thomas Monjalon
2019-01-17 18:19   ` Van Haaren, Harry
2019-02-06 16:16 ` Kevin Traynor

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=2654509.CpMWhpLgrV@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=harry.van.haaren@intel.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).