public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/112786] [14 Regression] gcc.dg/tree-ssa/scev-3.c scev-4.c and scev-5.c XPASSing on most ilp32 targets
Date: Sat, 09 Dec 2023 01:03:25 +0000 [thread overview]
Message-ID: <bug-112786-4-TbcLX5bq0n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112786-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112786
--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Hans-Peter Nilsson <hp@gcc.gnu.org>:
https://gcc.gnu.org/g:0f3bac474e8f6563a59f814ccf7609ced48b1157
commit r14-6353-g0f3bac474e8f6563a59f814ccf7609ced48b1157
Author: Hans-Peter Nilsson <hp@axis.com>
Date: Thu Dec 7 17:23:30 2023 +0100
testsuite: Remove gcc.dg/tree-ssa/scev-3.c -4.c and 5.c
These tests were recently xfailed on ilp32 targets though
passing on almost all ilp32 targets (known exceptions: ia32
and some arm subtargets). They've been changed around too
much to remain useful.
PR testsuite/112786
* gcc.dg/tree-ssa/scev-3.c, gcc.dg/tree-ssa/scev-4.c,
gcc.dg/tree-ssa/scev-5.c: Remove.
next prev parent reply other threads:[~2023-12-09 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:05 [Bug testsuite/112786] New: " hp at gcc dot gnu.org
2023-11-30 17:05 ` [Bug testsuite/112786] " hp at gcc dot gnu.org
2023-12-01 3:45 ` hp at gcc dot gnu.org
2023-12-01 7:21 ` rguenth at gcc dot gnu.org
2023-12-02 0:23 ` hp at gcc dot gnu.org
2023-12-09 1:03 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-09 18:07 ` hp 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-112786-4-TbcLX5bq0n@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).