From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: test-getgroups.c:stringop-overflow warning on newer GCC
Date: Sat, 2 Jan 2021 03:30:44 +0100 [thread overview]
Message-ID: <1918dba0-3f35-795d-df2c-48e107f725ea@bernhard-voelker.de> (raw)
In-Reply-To: <1825823.qd5lRurjMP@omega>
Hi Bruno,
On 1/2/21 2:59 AM, Bruno Haible wrote:
> Hi Berny,
>
>> So it may be an issue with the 10.2.1 version
>> ...
>> I'm not sure how to proceed from here.
>
> The most interesting piece of information is the rationale of this
> warning (i.e. more precisely why the warning is enabled by default).
> Maybe it can be found in the set of patches of this GCC version and/or
> its Changelog?
>
> Bruno
>
I can't find a trace about it. The GCC on my Tumbleweed is based on
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e563687cf9d3d1278f45aaebd
with only a handful of unrelated patches.
As I see the same on Fedora, the issue seems to be upstream, doesn't it?
Cloning 'gcc.git' with my slow connection takes a while. But I'm not sure
whether I'll be able to find something in the GCC sources after the tag
'releases/gcc-10.2.0' (your version).
Have a nice day,
Berny
next prev parent reply other threads:[~2021-01-02 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 22:57 test-getgroups.c:stringop-overflow warning on newer GCC Bernhard Voelker
2021-01-01 12:56 ` Bruno Haible
2021-01-02 1:43 ` Bernhard Voelker
2021-01-02 1:59 ` Bruno Haible
2021-01-02 2:30 ` Bernhard Voelker [this message]
2021-01-02 3:33 ` Paul Eggert
2021-01-02 12:51 ` Bruno Haible
2021-01-02 19:21 ` Bernhard Voelker
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1918dba0-3f35-795d-df2c-48e107f725ea@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).