public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95757] [11 regression] missing warning in gcc.dg/Wstringop-overflow-25.c since r11-1517
Date: Tue, 23 Feb 2021 02:59:11 +0000 [thread overview]
Message-ID: <bug-95757-4-QnjS1W7wSB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95757-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95757
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu.org
Status|WAITING |NEW
Last reconfirmed|2020-10-16 00:00:00 |2021-2-23
Target|powerpc64*-linux-gnu arm |powerpc64*-linux-gnu, arm,
| |cris, mmix, pru, moxie,
| |m68k
--- Comment #6 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
I was just about to open a new bug-report with the following observations, some
of which are not redundant:
Since commit 5acc654e3807 / r11-1517 the test gcc.dg/Wstringop-overflow-25.c
has
failed for cris-elf as follows, still at 8e99b5ba4c19 / r11-7328:
Running /x/gcc/gcc/testsuite/gcc.dg/dg.exp ...
... (elided lines)
FAIL: gcc.dg/Wstringop-overflow-25.c pr92814 (test for warnings, line 378)
The emitted warnings for the other lines of this tests are
the same for cris-elf as for x86_64-pc-linux-gnu (where the
test passes).
There's no apparent reason for this difference. For
example, it doesn't seem to have to do with alignment or
structure layout. The same missing error on the same line
can be seen for targets with widely different characteristics, like
for mmix-knuth-mmixware:
https://gcc.gnu.org/pipermail/gcc-testresults/2020-August/583266.html
and powerpc64le-unknown-linux-gnu:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652702.html
and pru-unknown-elf:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652712.html
and moxie-unknown-elf:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652743.html
and m68k-unknown-linux-gnu:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652763.html
but not for i686-linux-gnu:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652708.html
nor aarch64-none-elf -mabi=ilp32:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652767.html
nor arm-none-eabi DEFCPU=cortex-a9:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-February/652814.html
next prev parent reply other threads:[~2021-02-23 2:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 2:05 [Bug middle-end/95757] New: " seurer at linux dot vnet.ibm.com
2020-06-19 7:23 ` [Bug middle-end/95757] " rguenth at gcc dot gnu.org
2020-06-19 7:35 ` clyon at gcc dot gnu.org
2020-08-13 15:33 ` seurer at gcc dot gnu.org
2020-10-16 11:53 ` rguenth at gcc dot gnu.org
2020-10-16 12:03 ` clyon at gcc dot gnu.org
2020-12-16 18:14 ` seurer at gcc dot gnu.org
2021-02-23 2:59 ` hp at gcc dot gnu.org [this message]
2021-02-26 12:12 ` rguenth at gcc dot gnu.org
2021-03-01 14:48 ` jakub at gcc dot gnu.org
2021-03-01 17:59 ` jakub at gcc dot gnu.org
2021-03-02 10:49 ` cvs-commit at gcc dot gnu.org
2021-03-02 10:55 ` jakub at gcc dot gnu.org
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-95757-4-QnjS1W7wSB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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).