From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 395] Build of hinic with GCC 10.0.1 fails on aarch64
Date: Tue, 11 Feb 2020 11:10:20 +0000 [thread overview]
Message-ID: <bug-395-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=395
Bug ID: 395
Summary: Build of hinic with GCC 10.0.1 fails on aarch64
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/aarch64/dpdk/_log
[ 399s]
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/hinic/base/hinic_pmd_hwdev.c:
In function 'print_cable_info':
[ 399s]
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/hinic/base/hinic_pmd_hwdev.c:1398:3:
error: 'snprintf' argument 4 may overlap destination object 'tmp_str'
[-Werror=restrict]
[ 399s] 1398 | snprintf(tmp_str + strlen(tmp_str), (sizeof(tmp_str) - 1),
[ 399s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 399s] 1399 | "%s, Temperature: %u", tmp_str,
[ 399s] | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 399s] 1400 | info->cable_temp);
[ 399s] | ~~~~~~~~~~~~~~~~~
[ 399s]
/home/abuild/rpmbuild/BUILD/dpdk-1581015204.2636c2a23/drivers/net/hinic/base/hinic_pmd_hwdev.c:1363:7:
note: destination object referenced by 'restrict'-qualified argument 1 was
declared here
[ 399s] 1363 | char tmp_str[512] = {0};
[ 399s] | ^~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-02-11 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 11:10 bugzilla [this message]
2020-03-20 12:41 ` [dpdk-dev] [Bug 395] Build of hinic with GCC 10.0.1 fails on aarch64 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-395-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 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.