public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Adhemerval Zanella <azanella@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/azanella/clang] intl: Use strcpy on _nl_make_l10nflist Date: Wed, 17 Apr 2024 20:12:29 +0000 (GMT) [thread overview] Message-ID: <20240417201229.E7B663858D39@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=74bbd495acafd15d9ca790bc1c03ffcf6d3cfe38 commit 74bbd495acafd15d9ca790bc1c03ffcf6d3cfe38 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Wed Aug 10 17:56:13 2022 -0300 intl: Use strcpy on _nl_make_l10nflist It avoid compiler to turn is on strcpy, which might generate a strcpy PLT call since there is no explicit redirection. Diff: --- intl/l10nflist.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intl/l10nflist.c b/intl/l10nflist.c index 7eed651885..8ce64d30f6 100644 --- a/intl/l10nflist.c +++ b/intl/l10nflist.c @@ -210,7 +210,7 @@ _nl_make_l10nflist (struct loaded_l10nfile **l10nfile_list, } *cp++ = '/'; - stpcpy (cp, filename); + strcpy (cp, filename); /* Look in list of already loaded domains whether it is already available. */
next reply other threads:[~2024-04-17 20:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-17 20:12 Adhemerval Zanella [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-04-02 15:58 Adhemerval Zanella 2024-02-09 17:37 Adhemerval Zanella 2024-02-07 14:12 Adhemerval Zanella 2024-01-29 18:02 Adhemerval Zanella 2023-12-21 18:59 Adhemerval Zanella 2023-09-28 17:57 Adhemerval Zanella 2023-08-30 12:41 Adhemerval Zanella 2023-02-09 19:53 Adhemerval Zanella 2022-10-28 17:46 Adhemerval Zanella 2022-10-04 13:04 Adhemerval Zanella
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=20240417201229.E7B663858D39@sourceware.org \ --to=azanella@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).