public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102944] Many gcc.dg/Wstringop-overflow-*.c failures
Date: Wed, 03 Nov 2021 13:14:38 +0000 [thread overview]
Message-ID: <bug-102944-4-fcLmzZ1Tdh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102944-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102944
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
> The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:2e560abff4294639a0fcf666994c30fb2f00a324
>
> commit r12-4839-g2e560abff4294639a0fcf666994c30fb2f00a324
> Author: liuhongt <hongtao.liu@intel.com>
> Date: Thu Oct 28 14:28:29 2021 +0800
>
> Adjust testcase for O2 vect.
This patch seems to have caused
+FAIL: gcc.dg/Warray-bounds-48.c pr102706 (test for warnings, line 133)
+FAIL: gcc.dg/Warray-bounds-48.c pr102706 (test for warnings, line 33)
I'm seeing it on 64-bit sparc, and there are also reports for
s390x-ibm-linux-gnu and m68k-unknown-linux-gnu. It may be a
coincidance, but those are all big-endian targets.
next prev parent reply other threads:[~2021-11-03 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 14:00 [Bug testsuite/102944] New: " ro at gcc dot gnu.org
2021-10-26 14:00 ` [Bug testsuite/102944] " ro at gcc dot gnu.org
2021-10-28 1:19 ` crazylht at gmail dot com
2021-11-02 8:41 ` cvs-commit at gcc dot gnu.org
2021-11-03 13:14 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-11-04 5:31 ` crazylht at gmail dot com
2021-12-16 16:28 ` msebor at gcc dot gnu.org
2021-12-17 1:24 ` crazylht at gmail dot com
2021-12-17 12:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-17 15:26 ` msebor 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-102944-4-fcLmzZ1Tdh@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).