From: Markos Chandras <mchandras@suse.de>
To: Nirmoy Das <ndas@suse.de>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag
Date: Mon, 12 Jun 2017 17:35:22 +0300 [thread overview]
Message-ID: <fc20caed-14be-2181-e001-c4f7bbffb658@suse.de> (raw)
In-Reply-To: <af1738f9-f100-391c-e61d-00c013e70866@suse.de>
On 06/02/2017 07:38 PM, Markos Chandras wrote:
> On 06/02/2017 05:31 PM, Nirmoy Das wrote:
>> disable truncation check to ignore below warning
>> dpdk/x86_64-native-linuxapp-gcc-default/build/lib/librte_eal/linuxapp/kni/igb_main.c:2476:30: error: '%d' directive output may be truncated writing between 1 and 5 bytes into a region of size between 0 and 11 [-Werror=format-truncation=]
>>
>> Signed-off-by: Nirmoy Das <ndas@suse.de>
>> ---
>
> I haven't check the code but is this a bogus warning or a real one? If
> it's bogus then could you explain why in the commit message so we do not
> bring it back in the future? If it's a real problem, then perhaps worth
> fixing it instead of masking it?
>
Actually this should have already been fixed in the series posted in
http://dpdk.org/ml/archives/dev/2017-May/065261.html
--
markos
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
next prev parent reply other threads:[~2017-06-12 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 16:31 Nirmoy Das
2017-06-02 16:38 ` Markos Chandras
2017-06-12 14:35 ` Markos Chandras [this message]
2017-06-13 9:18 ` Nirmoy Das
2017-06-13 10:01 ` Markos Chandras
2017-06-13 13:45 ` Ferruh Yigit
2017-06-13 13:49 ` Markos Chandras
2017-06-13 16:50 ` Ferruh Yigit
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=fc20caed-14be-2181-e001-c4f7bbffb658@suse.de \
--to=mchandras@suse.de \
--cc=dev@dpdk.org \
--cc=ndas@suse.de \
/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).