From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Marc <marcdevel@gmail.com>, Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
Date: Wed, 17 Feb 2016 11:07:40 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8A67B0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAExC=0QD5OANsCZyG7--d6rO0bV_sU5XmgUjnPTeKWsX7OokvQ@mail.gmail.com>
Hi,
> From: marc.sune@gmail.com [mailto:marc.sune@gmail.com] On Behalf Of
> Marc
> Sent: Tuesday, February 16, 2016 11:19 PM
> To: Matthew Hall
> Cc: De Lara Guarch, Pablo; Mcnamara, John; dev@dpdk.org
> Subject: Re: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
>
>
>
> On 16 February 2016 at 19:47, Matthew Hall <mhall@mhcomputing.net>
> wrote:
> On Tue, Feb 16, 2016 at 12:57:24PM +0000, De Lara Guarch, Pablo wrote:
> > We suspect this might be an architecture dependent issue.
> > Could you tell us which CPU you are using?
> >
> > Thanks,
> > Pablo
>
> When it happens to me I am using a Skylake Core i7-6700K.
>
> Broadwell qemu emulated.
From what I have seen, this issue happens on Broadwell/Haswell with clang versions < 3.7.
This what I see when using clang 3.6.2:
clang -Wp,-MD,./.eal.o.d.tmp -m64 -pthread -march=native -DRTE_MACHINE_CPUFLAG_SSE
-DRTE_MACHINE_CPUFLAG_SSE2 -DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2
This is what I see with clang 3.7:
clang-3.7 -Wp,-MD,./.eal.o.d.tmp -m64 -pthread -march=native -DRTE_MACHINE_CPUFLAG_SSE
-DRTE_MACHINE_CPUFLAG_SSE2 -DRTE_MACHINE_CPUFLAG_SSE3 -DRTE_MACHINE_CPUFLAG_SSSE3
-DRTE_MACHINE_CPUFLAG_SSE4_1 -DRTE_MACHINE_CPUFLAG_SSE4_2 -DRTE_MACHINE_CPUFLAG_AES
-DRTE_MACHINE_CPUFLAG_PCLMULQDQ -DRTE_MACHINE_CPUFLAG_AVX -DRTE_MACHINE_CPUFLAG_RDRAND
-DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2,RTE_CPUFLAG_SSE3,
RTE_CPUFLAG_SSSE3,RTE_CPUFLAG_SSE4_1,RTE_CPUFLAG_SSE4_2,RTE_CPUFLAG_AES,
RTE_CPUFLAG_PCLMULQDQ,RTE_CPUFLAG_AVX,RTE_CPUFLAG_RDRAND
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
>
> Marc
>
>
> Matthew.
next prev parent reply other threads:[~2016-02-17 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:21 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 [this message]
2016-02-17 20:23 ` Matthew Hall
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=E115CCD9D858EF4F90C690B0DCB4D8973C8A67B0@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=marcdevel@gmail.com \
--cc=mhall@mhcomputing.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).