DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1743] malloc: duplicate shadowed variable definition
Date: Thu, 03 Jul 2025 17:06:16 +0000	[thread overview]
Message-ID: <bug-1743-3@https.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1743
           Summary: malloc: duplicate shadowed variable definition
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

Building with -Wshadow reports:

[51/3418] Compiling C object lib/librte_eal.a.p/eal_common_malloc_heap.c.o
../lib/eal/common/malloc_heap.c: In function ‘malloc_heap_free’:
../lib/eal/common/malloc_heap.c:1047:23: warning: declaration of ‘aligned_end’
shadows a previous local [-Wshadow]
 1047 |                 void *aligned_end = RTE_PTR_ADD(aligned_start,
aligned_len);
      |                       ^~~~~~~~~~~
../lib/eal/common/malloc_heap.c:862:45: note: shadowed declaration is here
  862 |         void *start, *aligned_start, *end, *aligned_end;
      |                                             ^~~~~~~~~~~

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

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

                 reply	other threads:[~2025-07-03 17:06 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-1743-3@https.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).