From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/31336] New: Glibc tests failed to compile with GCC 14
Date: Sun, 04 Feb 2024 03:09:53 +0000 [thread overview]
Message-ID: <bug-31336-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31336
Bug ID: 31336
Summary: Glibc tests failed to compile with GCC 14
Product: glibc
Version: 2.40
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: hjl.tools at gmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
I got
In file included from tests-mbwc/tst_iswalnum.c:7:
tests-mbwc/tsp_common.c: In function ?result.constprop.isra?:
tests-mbwc/tsp_common.c:55:43: error: ?%s? directive writing up to 92 bytes
into a region of size between 2 and 114 [-Werror=format-overflow=]
55 | sprintf (result_rec, "%s:%s:%d:%d:%d:%c:%s\n", func, loc, rec_no,
seq_no,
| ^~
tests-mbwc/tsp_common.c:55:3: note: ?sprintf? output between 20 and 224 bytes
into a destination of size 132
55 | sprintf (result_rec, "%s:%s:%d:%d:%d:%c:%s\n", func, loc, rec_no,
seq_no,
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
56 | case_no, res, msg);
| ~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[4]: *** [../o-iterator.mk:9:
/export/build/gnu/tools-build/glibc-test/build-x86_64-linux/localedata/tst_iswalnum.o]
Error 1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-02-04 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 3:09 hjl.tools at gmail dot com [this message]
2024-02-04 5:59 ` [Bug localedata/31336] " hjl.tools at gmail dot com
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=bug-31336-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).