DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1616] libtmp_rte_event_dlb2 sse fails to compile
Date: Fri, 17 Jan 2025 11:26:00 +0000	[thread overview]
Message-ID: <bug-1616-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1616
           Summary: libtmp_rte_event_dlb2 sse fails to compile
           Product: DPDK
           Version: 24.11
          Hardware: x86
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: eventdev
          Assignee: dev@dpdk.org
          Reporter: ivan@semenov.dev
  Target Milestone: ---

libtmp_rte_event_dlb2 fails to compile on CPUs without AVX512 support


On CPUs without AVX512 is used file dlb2_sse.c instead of dlb2_avx512.c and it
hasn't been updated in dpdk 24.11.
AVX512 varian is compiling without any issues


====================
FAILED: drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_sse.c.o 
cc -Idrivers/libtmp_rte_event_dlb2.a.p -Idrivers -I../drivers
-Idrivers/event/dlb2 -I../drivers/event/dlb2 -Ilib/eventdev -I../lib/eventdev
-I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include
-Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include
-I../lib/eal/x86/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common
-Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log
-Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/ring
-I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf
-I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/meter -I../lib/meter
-Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/timer -I../lib/timer
-Ilib/cryptodev -I../lib/cryptodev -Ilib/dmadev -I../lib/dmadev -Ilib/pci
-I../lib/pci -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra
-std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat
-Wformat-nonliteral -Wformat-security -Wmissing-declarations
-Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith
-Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings
-Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC
-march=native -mno-avx512f -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API
-Wno-format-truncation -Wno-address-of-packed-member
-DRTE_LOG_DEFAULT_LOGTYPE=pmd.event.dlb2 -MD -MQ
drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_sse.c.o -MF
drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_sse.c.o.d -o
drivers/libtmp_rte_event_dlb2.a.p/event_dlb2_dlb2_sse.c.o -c
../drivers/event/dlb2/dlb2_sse.c
../drivers/event/dlb2/dlb2_sse.c: In function 'dlb2_event_build_hcws':
../drivers/event/dlb2/dlb2_sse.c:193:28: error: 'struct dlb2_port' has no
member named 'cq_weight'
  193 |                 if (qm_port->cq_weight) {
      |    
====================

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

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

                 reply	other threads:[~2025-01-17 11:26 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-1616-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).