From: Hans-Peter Nilsson <hp@axis.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: <oliva@adacore.com>, <botcazou@adacore.com>, <rguenther@suse.de>,
<jeffreyalaw@gmail.com>, <ro@CeBiTec.Uni-Bielefeld.DE>,
<gcc-patches@gcc.gnu.org>, <mikestump@comcast.net>
Subject: Re: [PATCH] testsuite: scev: expect fail on ilp32
Date: Fri, 1 Dec 2023 03:38:15 +0100 [thread overview]
Message-ID: <20231201023815.29ECA2042C@pchp3.se.axis.com> (raw)
In-Reply-To: <20231130170910.5B7C720442@pchp3.se.axis.com> (message from Hans-Peter Nilsson on Thu, 30 Nov 2023 18:09:10 +0100)
> From: Hans-Peter Nilsson <hp@axis.com>
> Date: Thu, 30 Nov 2023 18:09:10 +0100
> I intend to post two alternative patches to get this
> resolved:
> 1: Move the tests to gcc.target/i386/scev-[3-5].c
> 2: gcc.dg/tree-ssa/scev-[3-5].c skipped for arm*, xfailed
> only on h8300-*-* and ia32.
Correction: h8300-elf does not XPASS not because it's a
ilp32 that fails, but because it's not an ilp32 and does not
match the XFAIL selector, therefore it passes.
IOW, minimizing the negations: h8300-elf is apparently an
"i16lp32" and passes. No need for special-casing.
TIL, TMRIF.
brgds, H-P
next prev parent reply other threads:[~2023-12-01 2:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 7:30 Alexandre Oliva
2023-11-19 15:12 ` Jeff Law
2023-11-20 7:35 ` Richard Biener
2023-11-28 15:13 ` Rainer Orth
2023-11-29 18:00 ` Hans-Peter Nilsson
2023-11-30 4:41 ` Alexandre Oliva
2023-11-30 8:32 ` Richard Biener
2023-11-30 17:09 ` Hans-Peter Nilsson
2023-12-01 2:38 ` Hans-Peter Nilsson [this message]
2023-12-01 3:35 ` Hans-Peter Nilsson
2023-12-01 7:07 ` Richard Biener
2023-12-01 23:18 ` Hans-Peter Nilsson
2023-12-04 11:58 ` Richard Biener
2023-12-07 16:33 ` Hans-Peter Nilsson
2023-12-07 21:03 ` Jeff Law
2023-12-08 6:46 ` Richard Biener
2023-12-01 3:41 ` Hans-Peter Nilsson
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=20231201023815.29ECA2042C@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=rguenther@suse.de \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).