DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: Ali Alnubani <alialnu@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] event/octeontx: add event timer adapter driver
Date: Mon, 23 Apr 2018 14:14:34 +0530	[thread overview]
Message-ID: <20180423084433.GA29406@ltp-pvn> (raw)
In-Reply-To: <VI1PR05MB4269C6391BE1991586F19421D78A0@VI1PR05MB4269.eurprd05.prod.outlook.com>

Hi Ali,

Looks like a compiler bug rather than code issue, I have verified this on x86
with gcc 4.8.5 and don't see an issue.

Looking around I found that compiling with -O1 on aarch64 gcc 4.8.5 seems to
fix the compiler bug.

Thanks,
Pavan.

On Sun, Apr 22, 2018 at 04:03:36PM +0000, Ali Alnubani wrote:
> Hi Pavan,
>
> The patchset http://dpdk.org/ml/archives/dev/2018-April/094928.html is causing a compilation error on QUALCOMM ARM with RHEL7.5 and gcc version 4.8.5:
>
> """
> /download/dpdk-next-net-mlx/drivers/event/octeontx/timvf_worker.c: In function 'timvf_timer_arm_burst_sp':
> /download/dpdk-next-net-mlx/drivers/event/octeontx/timvf_worker.c:89:1: error: could not split insn
> }
> ^
> (insn 95 98 99 (parallel [
>             (set (reg:DI 0 x0 [orig:98 D.8130 ] [98])
>                 (mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8136 ] [88]) [-1  S8 A64]))
>             (set (mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8136 ] [88]) [-1  S8 A64])
>                 (unspec_volatile:DI [
>                         (plus:DI (mem/v:DI (reg/f:DI 21 x21 [orig:88 D.8136 ] [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))
>         ]) /download/dpdk-next-net-mlx/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)))))
> /download/dpdk-next-net-mlx/drivers/event/octeontx/timvf_worker.c:89: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.
>   PMDINFO opdl_evdev.o.pmd.c
>   CC opdl_evdev.o.pmd.o
>   LD opdl_evdev.o
>   PMDINFO sw_evdev.o.pmd.c
>   CC sw_evdev.o.pmd.o
>   LD sw_evdev.o
> Preprocessed source stored into /tmp/ccmqxmH7.out file, please attach this to your bugreport.
> make[6]: *** [timvf_worker.o] Error 1
> make[5]: *** [octeontx] Error 2
> make[5]: *** Waiting for unfinished jobs....
>   AR librte_pmd_opdl_event.a
>   INSTALL-LIB librte_pmd_opdl_event.a
>   AR librte_pmd_sw_event.a
>   INSTALL-LIB librte_pmd_sw_event.a
> make[4]: *** [event] Error 2
> make[3]: *** [drivers] Error 2
> make[2]: *** [all] Error 2
> make[1]: *** [pre_install] Error 2
> make: *** [install] Error
> """
>
> The compilation only passes with CONFIG_RTE_LIBRTE_OCTEONTX_PMD, CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF and CONFIG_RTE_LIBRTE_OCTEONTX_MEMPOOL set to false.
> It also passes if I upgrade gcc, but can we have a fix for old gcc versions?
>
> Thanks,
> Ali

  reply	other threads:[~2018-04-23  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-22 16:03 Ali Alnubani
2018-04-23  8:44 ` Pavan Nikhilesh [this message]
2018-05-06 13:17   ` Shahaf Shuler
2018-05-06 13:33     ` Jerin Jacob
2018-05-07  5:30       ` Shahaf Shuler
2018-05-07  5:49         ` Jerin Jacob

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=20180423084433.GA29406@ltp-pvn \
    --to=pbhagavatula@caviumnetworks.com \
    --cc=alialnu@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=rasland@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=thomas@monjalon.net \
    /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).