public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@axis.com>
To: Richard Biener <rguenther@suse.de>
Cc: <oliva@adacore.com>, <gcc-patches@gcc.gnu.org>,
	<botcazou@adacore.com>, <jeffreyalaw@gmail.com>,
	<ro@CeBiTec.Uni-Bielefeld.DE>, <mikestump@comcast.net>
Subject: Re: [PATCH] testsuite: scev: expect fail on ilp32
Date: Sat, 2 Dec 2023 00:18:31 +0100	[thread overview]
Message-ID: <20231201231831.4238420424@pchp3.se.axis.com> (raw)
In-Reply-To: <5ro82896-4qq5-po26-12p5-97rnnoo31p37@fhfr.qr> (message from Richard Biener on Fri, 1 Dec 2023 08:07:14 +0100 (CET))

> Date: Fri, 1 Dec 2023 08:07:14 +0100 (CET)
> From: Richard Biener <rguenther@suse.de>

> On Fri, 1 Dec 2023, Hans-Peter Nilsson wrote:
> 
> > > From: Hans-Peter Nilsson <hp@axis.com>
> > > Date: Thu, 30 Nov 2023 18:09:10 +0100
> > 
> >     Richard B.:
> > > > > In the end we might need to move/duplicate the test to some
> > > > > gcc.target/* dir and restrict it to a specific tuning.
> > > 
> > > I intend to post two alternative patches to get this
> > > resolved:
> > > 1: Move the tests to gcc.target/i386/scev-[3-5].c
> > 
> > Subject: [PATCH 1/2] testsuite: Fix XPASS for gcc.dg/tree-ssa/scev-3.c, -4.c and -5.c [PR112786]
> > 
> > This is the first alternative, perhaps the more appropriate one.
> > 
> > Tested cris-elf, arm-eabi (default), x86_64-linux, ditto -m32,
> > h8300-elf and shle-linux; xpassing, skipped and passing as
> > applicable and intended.
> > 
> > Ok to commit?
> 
> Digging in history reveals the testcases were added by
> Jiangning Liu <jiangning.liu@arm.com>, not for any
> particular bugreport but "The problem is originally from a real benchmark,
> and the test case only tries to detect the GIMPLE level changes."
> 
> I'm not sure we can infer the testcase should be moved to
> gcc.target/arm/ because of that, but it does seem plausible.

It's been so long and so many changes since these tests were
regression guards, that the original target has lost
importance.  Heck, it was even xfail lp64 at one time!
According to my git dig, it's been adjusted for pass
changes, including reordering and dump output changes.  But
you know that; you've been instrumental in many of those
changes. :)

I'd say gcc.target/arm/ is the one target that's *not*
plausible, as according to Alex result differs between
subtargets.

> I read from your messages that the testcases pass on arm*-*-*?

Yes: they pass (currently XPASS) on arm-eabi and
arm-unknown-linux-gnueabi, default configurations.  But,
scev-3 and -5 fail with for example -mcpu=cortex-r5

brgds, H-P
PS. I'm open to just reverting the patch.  The s/ia32/ilp32/ is proven wrong.

  reply	other threads:[~2023-12-01 23:18 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
2023-12-01  3:35             ` Hans-Peter Nilsson
2023-12-01  7:07               ` Richard Biener
2023-12-01 23:18                 ` Hans-Peter Nilsson [this message]
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=20231201231831.4238420424@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).