public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24950] Top-of-tree glibc does not build with top-of-tree GCC (stringop-overflow error)
Date: Tue, 03 Sep 2019 12:57:00 -0000	[thread overview]
Message-ID: <bug-24950-716-YlvI6canrm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24950-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24950

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1471fa556afb428c4a4c46cf5543a4101d5bcf91

commit 1471fa556afb428c4a4c46cf5543a4101d5bcf91
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Sep 3 14:01:39 2019 +0200

    localedef: Use initializer for flexible array member [BZ #24950]

    struct charseq used a zero-length array instead of a flexible array
    member.  This required a strange construct to initialize struct
    charseq objects, and GCC 10 warns about that:

    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

    The change makes the object physically const, but it is not expected
    to be modified.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2019-09-03 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 18:59 [Bug localedata/24950] New: " sje at gcc dot gnu.org
2019-09-03 12:57 ` cvs-commit at gcc dot gnu.org [this message]
2019-09-03 13:00 ` [Bug localedata/24950] " 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-YlvI6canrm@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).