With those two items commented out, and these CFLAGS:
"-g -O0 -fPIC -msse4.2"
it looks like I can reproduce the issue in clang 2.6 series:
/vagrant/external/dpdk/build/include/rte_rtm.h:56:15: error: invalid operand
for inline asm constraint 'i'
asm volatile(".byte 0xc6,0xf8,%P0" :: "i" (status) : "memory");
So there are definitely some corner cases that seem to be able to trigger it.
On Jun 30, 2015, at 10:17 PM, Matthew Hall <mhall at mhcomputing.net> wrote:
> To be a bit more specific, this is what I had to do to fix it for clang 3.6
> SVN snapshot release.
>
> I am not sure if there is a better way of handling this situation. I'd love
> to know where I could improve it.
>
> Matthew.
>
> diff --git a/mk/rte.cpuflags.mk b/mk/rte.cpuflags.mk
> index f595cd0..8c883ee 100644
> --- a/mk/rte.cpuflags.mk
> +++ b/mk/rte.cpuflags.mk
> @@ -77,13 +77,13 @@ ifneq ($(filter $(AUTO_CPUFLAGS),__RDRND__),)
> CPUFLAGS += RDRAND
> endif
>
> -ifneq ($(filter $(AUTO_CPUFLAGS),__FSGSBASE__),)
> -CPUFLAGS += FSGSBASE
> -endif
> +#ifneq ($(filter $(AUTO_CPUFLAGS),__FSGSBASE__),)
> +#CPUFLAGS += FSGSBASE
> +#endif
>
> -ifneq ($(filter $(AUTO_CPUFLAGS),__F16C__),)
> -CPUFLAGS += F16C
> -endif
> +#ifneq ($(filter $(AUTO_CPUFLAGS),__F16C__),)
> +#CPUFLAGS += F16C
> +#endif
>
> ifneq ($(filter $(AUTO_CPUFLAGS),__AVX2__),)
> CPUFLAGS += AVX2
