From: Matthew Hall <mhall@mhcomputing.net>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: x86_64-native-linuxapp-clang compilation broken?
Date: Wed, 17 Feb 2016 12:23:13 -0800 [thread overview]
Message-ID: <20160217202313.GA26644@mhcomputing.net> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C8A67B0@IRSMSX108.ger.corp.intel.com>
On Wed, Feb 17, 2016 at 11:07:40AM +0000, De Lara Guarch, Pablo wrote:
> It looks like old versions of clang are not able to identify correctly the newer CPUs:
>
> LLVM (http://llvm.org/):
> LLVM version 3.6.2
>
> Optimized build.
> Built Aug 18 2015 (08:39:18).
> Default target: x86_64-pc-linux-gnu
> Host CPU: x86-64
>
>
> LLVM (http://llvm.org/):
> LLVM version 3.7.0
> Optimized build.
> Built Jan 22 2016 (17:39:46).
> Default target: x86_64-redhat-linux-gnu
> Host CPU: broadwell
>
> I will submit a patch adding a note in known issues section, unless anybody knows
> how to fix this in our side (as far as I know, it is a clang issue).
>
> Thanks,
> Pablo
Hello Pablo,
Just having some explanation of the root cause is a great start even if it
can't necessarily be fixed in DPDK. I will install clang 3.7.X and retry it.
Matthew.
prev parent reply other threads:[~2016-02-17 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:21 x86_64-native-linuxapp-clang compilation broken? Marc
2016-02-15 9:39 ` Mcnamara, John
2016-02-15 10:14 ` Van Haaren, Harry
2016-02-16 6:08 ` Matthew Hall
2016-02-15 9:44 ` Mcnamara, John
2016-02-16 11:49 ` Mcnamara, John
2016-02-16 12:15 ` Marc
2016-02-16 12:57 ` De Lara Guarch, Pablo
2016-02-16 18:47 ` Matthew Hall
2016-02-16 23:19 ` Marc
2016-02-17 11:07 ` De Lara Guarch, Pablo
2016-02-17 20:23 ` Matthew Hall [this message]
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=20160217202313.GA26644@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.