From: Andrew Pinski <pinskia@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: glibc master won't build with GCC 10
Date: Tue, 28 Apr 2020 16:08:37 -0700 [thread overview]
Message-ID: <CA+=Sn1mpqM2kW6X0LO+m4dqivs7YtvWMY1ATZbSB3r0XSdETHg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqQd5SA+esrk=mGZxk_07TyQEPRA+yasNf8gBPEiZLTNg@mail.gmail.com>
This should have been fixed already:
https://sourceware.org/bugzilla/show_bug.cgi?id=25097
Thanks,
Andrew
On Tue, Apr 28, 2020 at 3:54 PM H.J. Lu via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> commit 6d246cb852d3c5ab721dc583112a59ac47dc374e
> Author: Florian Weimer <fweimer@redhat.com>
> Date: Tue Apr 28 12:10:32 2020 +0200
>
> misc: Remove sstk from the autogenerated system call list
>
> This change should not have an effect because the system call was
> never defined. Also add the misssing attribute_compat_text_section
> attribute to the sstk function (a minor optimization). Also update the
> NEWS file to document the change.
>
> Fixes commit 9cc93ba0973ad04ee26c515a1552afb85e73c6ba
> ("misc: Turn sstk into a compat symbol").
>
> won't build with GCC 10:
>
> rtld.c: In function ‘dl_main’:
> rtld.c:1016:27: error: array subscript ‘cnt’ is outside the bounds of
> an interior zero-length array ‘struct auditstate[0]’
> [-Werror=zero-length-bounds]
> 1016 | GL(dl_rtld_map).l_audit[cnt].cookie = (intptr_t) &GL(dl_rtld_map);
> In file included from ../include/dlfcn.h:4,
> from rtld.c:20:
> ../include/link.h:335:7: note: while referencing ‘l_audit’
> 335 | } l_audit[0];
> | ^~~~~~~
> cc1: all warnings being treated as errors
> make[5]: *** [../o-iterator.mk:9:
> /export/build/gnu/tools-build/glibc/build-x86_64-linux/elf/rtld.os]
> Error 1
>
>
> --
> H.J.
next prev parent reply other threads:[~2020-04-28 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 21:57 H.J. Lu
2020-04-28 23:08 ` Andrew Pinski [this message]
2020-04-29 10:31 ` Florian Weimer
2020-04-29 12:44 ` H.J. Lu
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='CA+=Sn1mpqM2kW6X0LO+m4dqivs7YtvWMY1ATZbSB3r0XSdETHg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).