DPDK CI discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: David Marchand <david.marchand@redhat.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>,
	Luca Boccassi <bluca@debian.org>
Cc: nd <nd@arm.com>, dev <dev@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>, nd <nd@arm.com>
Subject: Re: [dpdk-ci] Compiler segfaults on arm ubuntu 18.04
Date: Thu, 15 Oct 2020 14:59:41 +0000	[thread overview]
Message-ID: <DBAPR08MB5814797E894BFF2EAD3837B698020@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8y3E7DF4VP+7xQsD+Z54B-+h0u_Wt4QcAL4+Bnbni4EPg@mail.gmail.com>

Thanks David. We had seen compiler segfaults internally in the past. Don't remember the versions which worked/did not work. We had to downgrade/upgrade the versions.
Are there plans to move to Ubuntu 20.04 or later?


> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, October 15, 2020 4:38 AM
> To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Ruifeng Wang
> <Ruifeng.Wang@arm.com>; Luca Boccassi <bluca@debian.org>
> Cc: nd <nd@arm.com>; dev <dev@dpdk.org>; ci@dpdk.org
> Subject: Compiler segfaults on arm ubuntu 18.04
> 
> This is not something new, as I noticed it quite a few times.
> 
> Reporting it now to see if you are aware of it and if we can do something
> about it.
> 
> We get gcc segfaults every once in a while in Travis:
> https://travis-ci.com/github/DPDK/dpdk/jobs/400035018#L1973
> 
> FAILED: drivers/drivers@@rte_pmd_failsafe@sha/meson-
> generated_.._rte_pmd_failsafe.pmd.c.o
> gcc -Idrivers/drivers@@rte_pmd_failsafe@sha -Idrivers -I../drivers -
> Idrivers/net/failsafe -I../drivers/net/failsafe -Ilib/librte_ethdev -
> I../lib/librte_ethdev -I. -I../ -Iconfig -I../config -Ilib/librte_eal/include -
> I../lib/librte_eal/include -Ilib/librte_eal/linux/include -
> I../lib/librte_eal/linux/include -Ilib/librte_eal/arm/include -
> I../lib/librte_eal/arm/include -Ilib/librte_eal/common -
> I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -
> I../lib/librte_kvargs -Ilib/librte_telemetry/../librte_metrics
> -I../lib/librte_telemetry/../librte_metrics -Ilib/librte_telemetry -
> I../lib/librte_telemetry -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -
> I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -
> Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_meter -I../lib/librte_meter -
> Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_pci -
> I../lib/librte_pci -Idrivers/bus/vdev -I../drivers/bus/vdev -fdiagnostics-
> color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O2
> -g -include rte_config.h -Wextra -Wcast-qual -Wdeprecated -Wformat-
> nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -
> Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -
> Wstrict-prototypes -Wundef -Wwrite-strings -Wno-missing-field-initializers -
> D_GNU_SOURCE -fPIC -DALLOW_EXPERIMENTAL_API -
> DALLOW_INTERNAL_API -Wno-format-truncation
> -std=gnu99 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 -pedantic -
> DLINUX -MD -MQ 'drivers/drivers@@rte_pmd_failsafe@sha/meson-
> generated_.._rte_pmd_failsafe.pmd.c.o'
> -MF 'drivers/drivers@@rte_pmd_failsafe@sha/meson-
> generated_.._rte_pmd_failsafe.pmd.c.o.d'
> -o 'drivers/drivers@@rte_pmd_failsafe@sha/meson-
> generated_.._rte_pmd_failsafe.pmd.c.o'
> -c drivers/rte_pmd_failsafe.pmd.c
> Segmentation fault
> 
> 
> Thanks.
> 
> --
> David Marchand


      reply	other threads:[~2020-10-15 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  9:38 David Marchand
2020-10-15 14:59 ` Honnappa Nagarahalli [this message]

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=DBAPR08MB5814797E894BFF2EAD3837B698020@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=bluca@debian.org \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.com \
    /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).