From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] meson: fix compilation with binutils version 2.30
Date: Thu, 17 Jan 2019 18:19:03 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA6757C25A6@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <2018846.8x2jbkSEOY@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Thursday, January 17, 2019 5:56 PM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] meson: fix compilation with binutils version
> 2.30
>
> 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 detected, disabling AVX512 support due to
> workaround for DPDK bugzilla bug #97')
>
> May I reword?
> Binutils 2.30 detected, disabling AVX512 support as workaround for bug
> #97
Yep sure, thanks!
next prev parent reply other threads:[~2019-01-17 18:19 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
2019-01-17 17:56 ` Thomas Monjalon
2019-01-17 18:19 ` Van Haaren, Harry [this message]
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=E923DB57A917B54B9182A2E928D00FA6757C25A6@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).