public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/109596] New: [14 Regression] Lots of testcases fails on x86_64 after r14-162-gcda246f8b421ba Date: Sun, 23 Apr 2023 01:46:24 +0000 [thread overview] Message-ID: <bug-109596-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109596 Bug ID: 109596 Summary: [14 Regression] Lots of testcases fails on x86_64 after r14-162-gcda246f8b421ba Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: haochen.jiang at intel dot com Target Milestone: --- Currently, we can see all the following testcases fail on x86_64: https://gcc.gnu.org/pipermail/gcc-regression/2023-April/077654.html From my bisect script, I can confirm that at least for pr90074 and pr90716, fail is casued by commit r14-162-gcda246f8b421ba. It seems that we might need to modify those testcases. Reproduce by: make check RUNTESTFLAGS="guality.exp=gcc.dg/guality/pr90716.c --target_board='unix{-m64\ -march=cascadelake,-m32\ -march=cascadelake,-m32,-m64}'"
next reply other threads:[~2023-04-23 1:46 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-23 1:46 haochen.jiang at intel dot com [this message] 2023-04-24 7:06 ` [Bug testsuite/109596] " rguenth at gcc dot gnu.org 2024-01-12 10:58 ` [Bug testsuite/109596] [14 Regression] Lots of guality testcase " rguenth at gcc dot gnu.org 2024-03-19 14:14 ` jakub at gcc dot gnu.org 2024-03-19 15:23 ` jakub at gcc dot gnu.org 2024-03-19 15:27 ` hubicka at gcc dot gnu.org 2024-03-19 15:41 ` jakub at gcc dot gnu.org 2024-03-19 15:47 ` hubicka at gcc dot gnu.org 2024-03-19 15:58 ` hubicka at gcc dot gnu.org 2024-03-19 16:28 ` jakub at gcc dot gnu.org 2024-03-19 22:28 ` jakub at gcc dot gnu.org 2024-03-20 11:50 ` jakub at gcc dot gnu.org 2024-04-10 7:13 ` rguenth at gcc dot gnu.org 2024-04-11 6:53 ` rguenth at gcc dot gnu.org 2024-04-11 9:11 ` cvs-commit at gcc dot gnu.org 2024-04-11 9:12 ` rguenth at gcc dot gnu.org 2024-04-12 18:14 ` carlos.seo at linaro dot org 2024-04-12 18:18 ` pinskia at gcc dot gnu.org 2024-04-12 18:24 ` carlos.seo at linaro dot org 2024-04-13 11:36 ` haochen.jiang at intel dot com 2024-04-15 18:53 ` hubicka 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-109596-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).