DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1197] Segmentation fault running acl_autotest when built with gcc 11 and -O3 on ppc64le
Date: Wed, 22 Mar 2023 16:43:09 +0000	[thread overview]
Message-ID: <bug-1197-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1197

            Bug ID: 1197
           Summary: Segmentation fault running acl_autotest when built
                    with gcc 11 and -O3 on ppc64le
           Product: DPDK
           Version: 23.03
          Hardware: POWER
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: drc@linux.vnet.ibm.com
  Target Milestone: ---

Building DPDK with gcc 11 (and later versions) on a ppc64le system with RHEL
8.7 produces a segmentation fault when running the acl_autotest:

$ meson build && meson test -C build --suite DPDK:fast-tests
...
[2397/2397] Linking target app/test/dpdk-test
 1/71 DPDK:fast-tests / acl_autotest                        FAIL            
1.27s   killed by signal 11 SIGSEGV
>>> MALLOC_PERTURB_=139 DPDK_TEST=acl_autotest
>>> /home/drc/src/dpdk/build/app/test/dpdk-test --no-huge -m 2048
>>> --file-prefix=acl_autotest

Building the same code with -O2 works correctly:

$ meson -Doptimization=2 build && meson test -C build --suite DPDK:fast-tests
...
[2397/2397] Linking target app/test/dpdk-test
 1/71 DPDK:fast-tests / acl_autotest                        OK              
2.72s
 2/71 DPDK:fast-tests / bitmap_autotest                     OK              
0.90s
...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3440 bytes --]

                 reply	other threads:[~2023-03-22 16:43 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=bug-1197-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).