From: Min Cao <min.cao@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [dpdk-stv] [PATCH 0/1] Fix the pointer 'ctx1' uninitialized error with gcc4.5.1
Date: Mon, 16 Jun 2014 11:22:10 +0800 [thread overview]
Message-ID: <1402888931-471-1-git-send-email-min.cao@intel.com> (raw)
Description: This patch is aimed to fix the the pointer 'ctx1' uninitialized error with gcc4.5.1 as described below.
Download dpdk source code from http://dpdk.org, and compile the source code(commit cc333208d5658fea642098b665cd429e6cda54a9).
It has the following compilation error on fedora14 with gcc4.5.1 while it is fine on Fedorak20 with gcc4.8.2:
"dpdk/lib/librte_kvargs/rte_kvargs.c:51:14: error: 'ctx1' may be used uninitialized in this function"
According to the latest DPDK OS Building Test Report(commit:cc333208d5658fea642098b665cd429e6cda54a9, the master branch from http://dpdk.org),
this error also occurs on SUSE11SP2_64 with gcc4.5.1, SUSE11SP3_32 with gcc4.5.1 and SUSE11SP3_64 with gcc4.3.4.
Initializing the pointer can solve this problem.
Signed-off-by: Cao Min <min.cao@intel.com>
Acked-by: Liu, Jijiang <jijiang.liu@intel.com>
Tested-by: Waterman Cao <waterman.cao@intel.com>
Zhan Zhaochen (1):
Fix the pointer 'ctx1' uninitialized error with gcc 4.5.1
lib/librte_kvargs/rte_kvargs.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
--
1.7.3.1
next reply other threads:[~2014-06-16 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 3:22 Min Cao [this message]
2014-06-16 3:22 ` [dpdk-dev] [dpdk-stv] [PATCH 1/1] Fix the pointer 'ctx1' uninitialized error with gcc 4.5.1 Min Cao
2014-06-17 17:04 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2014-06-16 1:45 [dpdk-dev] [dpdk-stv] [PATCH 0/1] Fix the pointer 'ctx1' uninitialized error with gcc4.5.1 min.cao
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=1402888931-471-1-git-send-email-min.cao@intel.com \
--to=min.cao@intel.com \
--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).