From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>, Richard Biener <rguenther@suse.de>
Cc: oliva@adacore.com, gcc-patches@gcc.gnu.org, botcazou@adacore.com,
ro@CeBiTec.Uni-Bielefeld.DE, mikestump@comcast.net
Subject: Re: [PATCH] testsuite: scev: expect fail on ilp32
Date: Thu, 7 Dec 2023 14:03:12 -0700 [thread overview]
Message-ID: <b8722a4d-6794-430e-978c-7454f4006426@gmail.com> (raw)
In-Reply-To: <20231207163345.1A90A2041E@pchp3.se.axis.com>
On 12/7/23 09:33, Hans-Peter Nilsson wrote:
>> Date: Mon, 4 Dec 2023 12:58:03 +0100 (CET)
>> From: Richard Biener <rguenther@suse.de>
>
>> On Sat, 2 Dec 2023, Hans-Peter Nilsson wrote:
>>>> Date: Fri, 1 Dec 2023 08:07:14 +0100 (CET)
>>>> From: Richard Biener <rguenther@suse.de>
>>>> 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
>>
>> I see. As said, the testcases test for "cost" things, so that we
>> "regressed" might mean we really "regressed" here. Even the x86 -m32
>> result is questionable.
>>
>> Of course whether using a single IV makes sense for all archs is
>> unknown.
>>
>> Btw, if we turn the testcases into ones that are (sub-)target
>> specific then we want to again use C code as input.
>>
>> I think at this point we've lost track and I'm juggling between
>> removing the testcases or moving them to a place they succeed
>> (with some specific -mcpu=?)
>>
>> Richard.
>
> So to not drop the ball(s) on this, here's a patch with your
> first alternative: remove them.
>
> Ok?
OK, but give Richard until Monday PM to chime in if he wants to try and
save them by putting them into a target specific directory.
jeff
next prev parent reply other threads:[~2023-12-07 21:03 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
2023-12-04 11:58 ` Richard Biener
2023-12-07 16:33 ` Hans-Peter Nilsson
2023-12-07 21:03 ` Jeff Law [this message]
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=b8722a4d-6794-430e-978c-7454f4006426@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.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).