From: David Christensen <drc@linux.vnet.ibm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] eal/ppc: ignore gcc 10 stringop-overflow warnings
Date: Wed, 28 Jul 2021 10:49:40 -0700 [thread overview]
Message-ID: <338d62a1-44bf-2fdc-c5b2-a0c3f75a6eb1@linux.vnet.ibm.com> (raw)
In-Reply-To: <deada627-62f5-3358-a653-ff1fc46e357a@linux.vnet.ibm.com>
On 7/12/21 12:35 PM, David Christensen wrote:
>
>
> On 7/5/21 2:28 AM, David Marchand wrote:
>> On Wed, Jun 23, 2021 at 6:13 PM David Christensen
>> <drc@linux.vnet.ibm.com> wrote:
>>>
>>> Suppress gcc warning "warning: writing 16 bytes into a region of
>>> size 0" for users of the POWER rte_memcpy() function. Existing
>>> rte_memcpy() code takes different code paths based on the actual
>>> size of the move so the warning is already addressed. See also
>>> commit b5b3ea803e47 ("eal/x86: ignore gcc 10 stringop-overflow
>>> warnings")
>>
>> Bugzilla ID: 739 ?
>
> Different compiler warning, though same gcc version involved.
>
>> What about a Cc: stable@dpdk.org?
>> We did backport such change for x86.
>
> Yes, should apply to stable as well. Do I need to resubmit patch or is
> the CC: enough?
Any reservations about including this in 21.08-rc3?
Dave
next prev parent reply other threads:[~2021-07-28 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 16:12 [dpdk-dev] " David Christensen
2021-07-05 9:28 ` David Marchand
2021-07-12 19:35 ` David Christensen
2021-07-28 17:49 ` David Christensen [this message]
2021-09-02 22:15 ` David Christensen
2021-09-08 17:42 ` David Christensen
2021-09-13 7:19 ` David Marchand
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=338d62a1-44bf-2fdc-c5b2-a0c3f75a6eb1@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@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).