From: "sje at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24950] New: Top-of-tree glibc does not build with top-of-tree GCC (stringop-overflow error)
Date: Thu, 29 Aug 2019 18:59:00 -0000 [thread overview]
Message-ID: <bug-24950-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24950
Bug ID: 24950
Summary: Top-of-tree glibc does not build with top-of-tree GCC
(stringop-overflow error)
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: sje at gcc dot gnu.org
CC: libc-locales at sourceware dot org
Target Milestone: ---
This bug is discussed at
https://sourceware.org/ml/libc-alpha/2019-08/msg00774.html. The GCC folks
think that the Glibc sources should be changed to avoid this warning/error.
From email string:
I am building the latest glibc with the latest GCC and getting an error.
I see where, in locale/programs/charmap.h we declare bytes as a zero
length array in charseq but I am not sure where the write in
locale/programs/ld-ctype.c is. The only line references that GCC seems
to be outputing refer to the declaration.
cc1: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
In file included from programs/repertoire.h:24,
from programs/localedef.h:32,
from programs/ld-ctype.c:35:
programs/charmap.h:63:17: note: destination object declared here
63 | unsigned char bytes[0];
| ^~~~~
cc1: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
programs/charmap.h:63:17: note: destination object declared here
cc1: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
programs/charmap.h:63:17: note: destination object declared here
cc1: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
programs/charmap.h:63:17: note: destination object declared here
cc1: all warnings being treated as errors
../o-iterator.mk:9: recipe for target '/home/sellcey/tot/obj/glibc64/locale/ld-
ctype.o' failed
make[2]: *** [/home/sellcey/tot/obj/glibc64/locale/ld-ctype.o] Error 1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-08-29 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 18:59 sje at gcc dot gnu.org [this message]
2019-09-03 12:57 ` [Bug localedata/24950] " cvs-commit at gcc dot gnu.org
2019-09-03 13:00 ` fweimer at redhat dot com
2019-09-03 13:01 ` fweimer at redhat dot com
2019-09-03 13:01 ` fweimer at redhat 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-24950-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).