From: sys_stv@intel.com
To: jianfeng.tan@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw11075 eal: make hugetlb initialization more robust
Date: 06 Mar 2016 23:23:53 -0800 [thread overview]
Message-ID: <acb6cf$ro06ca@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: compile error
Patchwork ID: 11075
http://www.dpdk.org/dev/patchwork/patch/11075/
Submitter: Jianfeng Tan <jianfeng.tan@intel.com>
Date: Fri, 4 Mar 2016 18:58:12 +0800
DPDK git baseline: 8827234d70dfc0b92f893f73d43af2275d354df9
Check patch:Success
Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
x86_64-native-linuxapp-gcc-combined: compile error
i686-native-linuxapp-gcc: compile error
x86_64-native-linuxapp-gcc: compile error
x86_64-native-linuxapp-clang: compile error
x86_64-native-linuxapp-gcc-shared: compile error
x86_64-native-linuxapp-gcc-debug: compile error
error info:
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c: In function .map_all_hugepages.constprop.7.:
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:332:11: error: variable .i. might be clobbered by .longjmp. or .vfork. [-Werror=clobbered]
unsigned i;
^
/home/patchWorkOrg/compilation/lib/librte_eal/linuxapp/eal/eal_memory.c:334:8: error: variable .vma_addr. might be clobbered by .longjmp. or .vfork. [-Werror=clobbered]
void *vma_addr = NULL;
^
cc1: all warnings being treated as errors
make[7]: *** [eal_memory.o] Error 1
make[6]: *** [eal] Error 2
make[5]: *** [linuxapp] Error 2
make[4]: *** [librte_eal] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2
DPDK STV team
reply other threads:[~2016-03-07 7:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='acb6cf$ro06ca@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=test-report@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).