From: Jeff Johnston <jjohnstn@redhat.com>
To: Alexey Lapshin <alexey.lapshin@espressif.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>,
Alexey Gerenkov <alexey.gerenkov@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>
Subject: Re: [PATCH v2] libc: fix __time_load_locale return code
Date: Wed, 17 May 2023 17:49:08 -0400 [thread overview]
Message-ID: <CAOox84tWbD00R5PQ-HLashif7iMs1W4vj2NEKaodWPa95D3tig@mail.gmail.com> (raw)
In-Reply-To: <CAOox84tsJr=yavSfc3N0ZLJpBgMLzcQ17OY=0bQgP-FPujvn5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]
Hi Alexey,
After thinking about it, the macro check is fine. I have checked in the
patch.
Thanks,
-- Jeff J.
On Wed, May 17, 2023 at 3:37 PM Jeff Johnston <jjohnstn@redhat.com> wrote:
> Hi Alexey,
>
> I see the point for adding the ret=0 but the additional flag check isn't
> needed because the function is meant to only be called by __loadlocale()
> which doesn't make the call unless __HAVE_LOCALE_INFO__ is set. If you
> want, I can make the change or else you can resubmit the patch.
>
> -- Jeff J.
>
> On Mon, May 15, 2023 at 12:30 PM Alexey Lapshin <
> alexey.lapshin@espressif.com> wrote:
>
>> newlib:
>> * libc/locale/timelocal.c: fix ret variable initialization.
>> Explicit __HAVE_LOCALE_INFO__ check
>> ---
>> newlib/libc/locale/timelocal.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/newlib/libc/locale/timelocal.c
>> b/newlib/libc/locale/timelocal.c
>> index 4b361544a..04ae1142f 100644
>> --- a/newlib/libc/locale/timelocal.c
>> +++ b/newlib/libc/locale/timelocal.c
>> @@ -147,10 +147,11 @@ int
>> __time_load_locale (struct __locale_t *locale, const char *name,
>> void *f_wctomb, const char *charset)
>> {
>> - int ret;
>> + int ret = 0;
>> struct lc_time_T ti;
>> char *bufp = NULL;
>>
>> +#ifdef __HAVE_LOCALE_INFO__
>> #ifdef __CYGWIN__
>> extern int __set_lc_time_from_win (const char *, const struct
>> lc_time_T *,
>> struct lc_time_T *, char **, void *,
>> @@ -186,5 +187,6 @@ __time_load_locale (struct __locale_t *locale, const
>> char *name,
>> #else
>> /* TODO */
>> #endif
>> +#endif /*__HAVE_LOCALE_INFO__*/
>> return (ret);
>> }
>> --
>> 2.34.1
>>
>
prev parent reply other threads:[~2023-05-17 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 6:32 [PATCH] " Alexey Lapshin
2023-05-15 16:30 ` [PATCH v2] " Alexey Lapshin
2023-05-17 19:37 ` Jeff Johnston
2023-05-17 21:49 ` Jeff Johnston [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=CAOox84tWbD00R5PQ-HLashif7iMs1W4vj2NEKaodWPa95D3tig@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=alexey.gerenkov@espressif.com \
--cc=alexey.lapshin@espressif.com \
--cc=ivan@espressif.com \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).