All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Bezdeka,
	Florian (T RDA IOT SES-DE)" <florian.bezdeka@siemens.com>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [PATCH v2] lib/boilerplate/iniparser: Allow building with GCC 10.2 2020101
Date: Thu, 12 Nov 2020 17:19:44 +0100	[thread overview]
Message-ID: <0511e991-534e-8bef-2fb0-a7a94c506f32@siemens.com> (raw)
In-Reply-To: <20201112114510.60332-1-florian.bezdeka@siemens.com>

On 12.11.20 12:45, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> From: Florian Bezdeka <florian.bezdeka@siemens.com>
> 
> Updating to upstream revision f858275f7f307eecba84c2f5429483f9f28007f8.
> 
> The reason for updating was the following compiler error when trying
> to compile with GCC 10.2 10.2.1 20201016. As it turned out the problem
> was already addressed upstream:
> 
> iniparser/iniparser.c: In function ‘iniparser_load’:
> iniparser/iniparser.c:616:13: error: ‘sprintf’ arguments 3, 4 may
> overlap destination object ‘buf’ [-Werror=restrict]
>    616 |             sprintf(tmp, "%s:%s", section, key);
>        |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> I reviewed especially the API changes. Most of them are cleanups only
> but two things should be pointed out:
> 
>   - The type of the size field of struct _dictionary_ changed from int
>     to ssize_t. The only user of this struct is
>     lib/analogy/calibration.c which uses this structure for internal
>     things only. It is never exposed to any public API so updating is
>     OK and fully backward compatible.
> 
>   - dictionary_new changed its signature
>       from dictionary_new(int size)
>       to   dictionary_new(size_t size).
>     This function is not part of any public API. So updating does not
>     break backward compatibility.
> 
> Signed-off-by: Florian Bezdeka <florian.bezdeka@siemens.com>
> ---
>  lib/boilerplate/iniparser/dictionary.c | 409 ++++++++++----------
>  lib/boilerplate/iniparser/dictionary.h |  43 ++-
>  lib/boilerplate/iniparser/iniparser.c  | 491 +++++++++++++++++--------
>  lib/boilerplate/iniparser/iniparser.h  | 131 +++++--
>  4 files changed, 646 insertions(+), 428 deletions(-)
> 

Thanks, applied to next (after sorting out our Siemens-local mail
transfer problem...).

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux



      reply	other threads:[~2020-11-12 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 14:59 [PATCH] lib/boilerplate: Allow building with GCC 10.2 florian.bezdeka
2020-11-12  6:58 ` Jan Kiszka
2020-11-12  8:49   ` florian.bezdeka
2020-11-12 11:45     ` [PATCH v2] lib/boilerplate/iniparser: Allow building with GCC 10.2 2020101 florian.bezdeka
2020-11-12 16:19       ` Jan Kiszka [this message]

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=0511e991-534e-8bef-2fb0-a7a94c506f32@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.