DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "bugzilla@dpdk.org" <bugzilla@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Bug 82] Failure to compile l3fwd example on ARM
Date: Wed, 15 Aug 2018 22:42:24 +0000	[thread overview]
Message-ID: <AM6PR08MB3672C0A6C931B3EE57F0F6ED983F0@AM6PR08MB3672.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <bug-82-3@http.bugs.dpdk.org/>

Thanks for raising the bug. Can you please provide the GCC version you are using?

Thanks,
Honnappa

-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of bugzilla@dpdk.org
Sent: Wednesday, August 15, 2018 6:10 AM
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 82] Failure to compile l3fwd example on ARM

https://bugs.dpdk.org/show_bug.cgi?id=82

            Bug ID: 82
           Summary: Failure to compile l3fwd example on ARM
           Product: DPDK
           Version: unspecified
          Hardware: ARM
                OS: Linux
            Status: CONFIRMED
          Severity: major
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: rasland@mellanox.com
  Target Milestone: ---

we can't compile l3fwd example application on ARM machines:

export RTE_SDK=~/dpdk/
export RTE_TARGET=arm64-armv8a-linuxapp-gcc

make
  CC main.o
  CC l3fwd_lpm.o
  CC l3fwd_em.o
~/dpdk/examples/l3fwd/l3fwd_em.c:244:2: error: #error No vector engine (SSE, NEON, ALTIVEC) available, check your toolchain  #error No vector engine (SSE, NEON, ALTIVEC) available, check your toolchain
  ^
~/dpdk/examples/l3fwd/l3fwd_em.c: In function ‘em_get_ipv4_dst_port’:
~/dpdk/examples/l3fwd/l3fwd_em.c:261:2: error: implicit declaration of function ‘em_mask_key’ [-Werror=implicit-function-declaration]
  key.xmm = em_mask_key(ipv4_hdr, mask0.x);
  ^
~/dpdk/examples/l3fwd/l3fwd_em.c:261:2: error: nested extern declaration of ‘em_mask_key’ [-Werror=nested-externs]
~/dpdk/examples/l3fwd/l3fwd_em.c:261:10: error: incompatible types when assigning to type ‘xmm_t’ from type ‘int’
  key.xmm = em_mask_key(ipv4_hdr, mask0.x);
          ^
~/dpdk/examples/l3fwd/l3fwd_em.c: In function ‘em_get_ipv6_dst_port’:
~/dpdk/examples/l3fwd/l3fwd_em.c:282:13: error: incompatible types when assigning to type ‘xmm_t’ from type ‘int’
  key.xmm[0] = em_mask_key(data0, mask1.x);
             ^
~/dpdk/examples/l3fwd/l3fwd_em.c:294:13: error: incompatible types when assigning to type ‘xmm_t’ from type ‘int’
  key.xmm[2] = em_mask_key(data2, mask2.x);
             ^
cc1: all warnings being treated as errors
make[1]: *** [l3fwd_em.o] Error 1
make: *** [all] Error 2

--
You are receiving this mail because:
You are the assignee for the bug.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

      reply	other threads:[~2018-08-15 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 11:09 bugzilla
2018-08-15 22:42 ` Honnappa Nagarahalli [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=AM6PR08MB3672C0A6C931B3EE57F0F6ED983F0@AM6PR08MB3672.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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).