DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 856] gcc12 build error, app/test-flow-perf
Date: Thu, 28 Oct 2021 12:38:41 +0000	[thread overview]
Message-ID: <bug-856-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 856
           Summary: gcc12 build error, app/test-flow-perf
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: ferruh.yigit@intel.com
  Target Milestone: ---

With gcc 12.0.0 "gcc (GCC) 12.0.0 20211024 (experimental)"

[1/2] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_main.c.o      
../app/test-flow-perf/main.c: In function ‘start_forwarding’:                   
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]            
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^                                            
In function ‘pretty_number’,                                                    
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1620:4,                            
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~             
../app/test-flow-perf/main.c: In function ‘start_forwarding’:
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^
In function ‘pretty_number’,
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1620:4,
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test-flow-perf/main.c: In function ‘start_forwarding’:
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^
In function ‘pretty_number’,
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1620:4,
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test-flow-perf/main.c: In function ‘start_forwarding’:
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^
In function ‘pretty_number’,
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1634:4,
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test-flow-perf/main.c: In function ‘start_forwarding’:
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^
In function ‘pretty_number’,
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1634:4,
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../app/test-flow-perf/main.c: In function ‘start_forwarding’:
../app/test-flow-perf/main.c:1565:28: warning: ‘sprintf’ may write a
terminating nul past the end of the destination [-Wformat-overflow=]
 1565 |         sprintf(p[i++], "%d", (int)n);
      |                            ^
In function ‘pretty_number’,
    inlined from ‘packet_per_second_stats’ at
../app/test-flow-perf/main.c:1634:4,
    inlined from ‘start_forwarding’ at ../app/test-flow-perf/main.c:1659:3:
../app/test-flow-perf/main.c:1565:9: note: ‘sprintf’ output between 2 and 5
bytes into a destination of size 4
 1565 |         sprintf(p[i++], "%d", (int)n);
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

             reply	other threads:[~2021-10-28 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 12:38 bugzilla [this message]
2022-06-15  8:38 ` bugzilla

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-856-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).