From: Martin Sebor via Libc-alpha <libc-alpha@sourceware.org>
To: Jeff Law <jeffreyalaw@gmail.com>,
Aldy Hernandez <aldyh@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
Martin Sebor <msebor@redhat.com>,
libc-alpha@sourceware.org
Subject: Re: Failures building glibc with mainline GCC
Date: Fri, 30 Jul 2021 11:28:44 -0600 [thread overview]
Message-ID: <768a6da5-9435-dc3d-9e29-57ccbd21c2a3@gmail.com> (raw)
In-Reply-To: <ff7f89db-9189-f8ce-ee1e-f64cfb01fbf3@gmail.com>
On 7/30/21 10:45 AM, Jeff Law via Gcc wrote:
>
>
> On 7/30/2021 10:19 AM, Aldy Hernandez via Libc-alpha wrote:
>> There's a new jump threader in GCC which is much more aggressive, and
>> may trigger latent problems with other warning passes, especially
>> -Warray-bounds, -Woverflow, and -Wuninitialized.
> [ ... ]
> Ugh. First attempt got blocked as message was slightly too big.
>
> I think this is pretty generic as I've seen it on multiple ports and
> Joseph mentioned them as well.
>
> With an s390-linux-gnu (not s390x!) cross compiler you should be able to
> trigger:
>
> bash-5.1# s390-linux-gnu-gcc -std=gnu99 -O2 -Wall -mlong-double-128 *.i
> In file included from t.61.c:437:
> In function 'from_t_61_single',
> inlined from 'gconv' at ../iconv/skeleton.c:568:15:
> ../iconv/loop.c:440:22: warning: writing 1 byte into a region of size 0
> [-Wstringop-overflow=]
> In file included from t.61.c:437:
> ../iconv/loop.c: In function 'gconv':
> ../iconv/loop.c:382:17: note: at offset 2 into destination object
> 'bytebuf' of size 2
>
>
> I don't know if it's a real failure or a false positive. I haven't even
> bisected, but I suspect the new threader is the triggering change.
> Ideally the threader threaded a path we hadn't previously and by some
> chain of events exposed a out of bounds write that needs to be fixed.
The warning is valid for the IL. Bytebuf is unsigned char[2] and
in bb 25 the warning sees:
<bb 25> [local count: 2288797]:
_613 = *inptr_96;
bytebuf[2] = _613; <<< -Wstringop-overflow
goto <bb 32>; [100.00%]
GCC can't tell if the code is reachable and neither can I. As
far as I can see it's the result of unrolling one if the loops
in the function, likely this one:
do
bytebuf[inlen++] = *inptr++;
while (inlen < 2 && inptr < inend);
Adding:
if (inlen >= 2) __builtin_unreachable ();
just above it avoids the warning.
Martin
next prev parent reply other threads:[~2021-07-30 17:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:30 Failures building glibc with mainline GCC Joseph Myers
2021-07-30 16:19 ` Aldy Hernandez via Libc-alpha
2021-07-30 16:22 ` Jeff Law via Libc-alpha
2021-07-30 16:45 ` Jeff Law via Libc-alpha
2021-07-30 17:28 ` Martin Sebor via Libc-alpha [this message]
2021-07-30 20:52 ` Joseph Myers
2021-08-02 20:20 ` Martin Sebor via Libc-alpha
2021-08-03 15:54 ` Joseph Myers
2021-08-03 16:20 ` Martin Sebor via Libc-alpha
2021-08-03 17:21 ` Joseph Myers
2021-08-03 17:39 ` Samuel Thibault via Libc-alpha
2021-08-03 22:33 ` Martin Sebor via Libc-alpha
2021-08-03 20:50 ` Segher Boessenkool
2021-08-03 21:00 ` Joseph Myers
2021-08-03 22:02 ` Segher Boessenkool
2021-08-03 22:59 ` Martin Sebor via Libc-alpha
2021-07-30 16:38 ` Joseph Myers
2021-07-30 16:43 ` Jakub Jelinek via Libc-alpha
2021-07-30 16:53 ` Martin Sebor via Libc-alpha
2021-07-30 17:02 ` Jakub Jelinek via Libc-alpha
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://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=768a6da5-9435-dc3d-9e29-57ccbd21c2a3@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=joseph@codesourcery.com \
--cc=msebor@gmail.com \
--cc=msebor@redhat.com \
/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).