DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 396] Build of octeontx2 with GCC 10.0.1 fails on armv7
Date: Tue, 11 Feb 2020 11:12:35 +0000	[thread overview]
Message-ID: <bug-396-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 396
           Summary: Build of octeontx2 with GCC 10.0.1 fails on armv7
           Product: DPDK
           Version: 20.02
          Hardware: ARM
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: luca.boccassi@gmail.com
  Target Milestone: ---

https://build.opensuse.org/build/home:bluca:dpdk/Fedora_Rawhide/armv7l/dpdk/_log

[  738s] In file included from
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/octeontx2/otx2_ethdev.h:24,
[  738s]                  from
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/octeontx2/otx2_rx.c:7:
[  738s]
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/octeontx2/otx2_rx.c:
In function 'otx2_nix_recv_pkts_no_offload':
[  738s]
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/octeontx2/otx2_rx.h:310:2:
error: array subscript 0 is outside the bounds of an interior zero-length array
'RTE_MARKER64' {aka 'long long unsigned int[0]'} [-Werror=zero-length-bounds]
[  738s]   310 |  *(uint64_t *)(&mbuf->rearm_data) = val;
[  738s]       |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-02-11 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 11:12 bugzilla [this message]
2020-05-19  9:37 ` bugzilla

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=bug-396-3@http.bugs.dpdk.org/ \
    --to=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).