From: =?gb18030?B?eWFuZw==?= <yangctl@qq.com>
To: =?gb18030?B?dXNlcnM=?= <users@dpdk.org>
Subject: [dpdk-users] dpdk-18.11 error
Date: Wed, 19 Dec 2018 10:44:13 +0800 [thread overview]
Message-ID: <tencent_14B578E706896C6124261FEE297C76C23108@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1708 bytes --]
== Build drivers/event/octeontx
CC timvf_worker.o
/home/dpdk/dpdk-18.11/drivers/event/octeontx/timvf_worker.c: In function ¡®timvf_timer_arm_burst_sp¡¯:
/home/dpdk/dpdk-18.11/drivers/event/octeontx/timvf_worker.c:88:1: error: could not split insn
}
^
(insn 95 98 99 (parallel [
(set (reg:DI 0 x0 [orig:98 D.8605 ] [98])
(mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8611 ] [88]) [-1 S8 A64]))
(set (mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8611 ] [88]) [-1 S8 A64])
(unspec_volatile:DI [
(plus:DI (mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8611 ] [88]) [-1 S8 A64])
(const_int -281474976710656 [0xffff000000000000]))
(const_int 0 [0])
] UNSPECV_ATOMIC_OP))
(clobber (reg:CC 66 cc))
(clobber (reg:DI 1 x1))
(clobber (reg:SI 2 x2))
]) /home/dpdk/dpdk-18.11/drivers/event/octeontx/timvf_worker.h:95 1832 {atomic_fetch_adddi}
(expr_list:REG_UNUSED (reg:CC 66 cc)
(expr_list:REG_UNUSED (reg:SI 2 x2)
(expr_list:REG_UNUSED (reg:DI 1 x1)
(nil)))))
/home/dpdk/dpdk-18.11/drivers/event/octeontx/timvf_worker.c:88:1: internal compiler error: in final_scan_insn, at final.c:2897
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/ccC4dTuH.out file, please attach this to your bugreport.
make[4]: *** [timvf_worker.o] Error 1
make[3]: *** [octeontx] Error 2
make[2]: *** [event] Error 2
make[1]: *** [drivers] Error 2
make: *** [all] Error 2
next reply other threads:[~2018-12-19 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 2:44 =?gb18030?B?eWFuZw==?= [this message]
2018-12-20 10:50 ` Andrew Bainbridge
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=tencent_14B578E706896C6124261FEE297C76C23108@qq.com \
--to=yangctl@qq.com \
--cc=users@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).