public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/102944] New: Many gcc.dg/Wstringop-overflow-*.c failures Date: Tue, 26 Oct 2021 14:00:11 +0000 [thread overview] Message-ID: <bug-102944-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102944 Bug ID: 102944 Summary: Many gcc.dg/Wstringop-overflow-*.c failures Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: crazylht at gmail dot com Target Milestone: --- Target: sparc-sun-solaris2.11, m68k-unknown-linux-gnu, moxie-unknown-elf, aarch64-suse-linux-gnu, mipsel-mti-elf, arm-none-linux-gnueabihf Between 20211019 (ff0eec94e87dfb7dc387f120ca5ade2707aecf50) and 20211020 (d98626bf451dea6a28a42d953f7d0bd7659ad4d5), quite a number of testsuite failures occured. I'm seeing them on Solaris/SPARC (32 and 64-bit), but gcc-testresults show reports for many others: +FAIL: gcc.dg/Warray-parameter-3.c pr102706 (test for warnings, line 80) +FAIL: gcc.dg/Wstringop-overflow-14.c pr102706 (test for warnings, line 39) +XPASS: gcc.dg/Wstringop-overflow-14.c pr102706 (test for warnings, line 40) +FAIL: gcc.dg/Wstringop-overflow-68.c pr101475 (test for warnings, line 68) +FAIL: gcc.dg/Wstringop-overflow-68.c pr101475 (test for warnings, line 69) +XPASS: gcc.dg/Wstringop-overflow-68.c pr101475 (test for warnings, line 70) +XPASS: gcc.dg/Wstringop-overflow-68.c pr101475 (test for warnings, line 71) +XPASS: gcc.dg/Wstringop-overflow-68.c pr101475 (test for warnings, line 72) +XPASS: gcc.dg/Wstringop-overflow-76.c note (test for warnings, line 107) +XPASS: gcc.dg/Wstringop-overflow-76.c note (test for warnings, line 86) +XPASS: gcc.dg/Wstringop-overflow-76.c pr102697 (test for warnings, line 119) +XPASS: gcc.dg/Wstringop-overflow-76.c pr102697 (test for warnings, line 99) +FAIL: gcc.dg/Wstringop-overflow-76.c pr102706 (test for warnings, line 30) +XPASS: gcc.dg/Wstringop-overflow-76.c pr102706 (test for warnings, line 33) +FAIL: gcc.dg/Wstringop-overflow-76.c pr102706 (test for warnings, line 47) +XPASS: gcc.dg/Wstringop-overflow-76.c pr102706 (test for warnings, line 50) AFAICS they are due to commit 3c8d8c0be95e99dc0cba7f6fad2429243582119f Author: liuhongt <hongtao.liu@intel.com> Date: Thu Oct 14 09:31:03 2021 +0800 Adjust testcase for O2 vectorization.
next reply other threads:[~2021-10-26 14:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 14:00 ro at gcc dot gnu.org [this message] 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 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@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: linkBe 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).