From: Richard Biener <rguenther@suse.de>
To: Sam James <sam@gentoo.org>
Cc: gcc-patches@gcc.gnu.org, pinskia@gcc.gnu.org, rguenth@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Add testcase for sparc ICE [PR105573]
Date: Mon, 24 Apr 2023 07:36:15 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2304240735350.4466@jbgna.fhfr.qr> (raw)
In-Reply-To: <20230421193338.3874230-1-sam@gentoo.org>
On Fri, 21 Apr 2023, Sam James wrote:
> r11-10018-g33914983cf3734c2f8079963ba49fcc117499ef3 fixed PR105312 and added
> a test case for target/arm but the duplicate PR105573 has a test case for
> target/sparc that was uncommitted until now.
OK. But see below for a question
> 2023-04-21 Sam James <sam@gentoo.org>
> PR tree-optimization/105312
> PR target/105573
> * gcc/testsuite/gcc.target/sparc/pr105573.c: New test.
>
> Signed-off-by: Sam James <sam@gentoo.org>
> ---
> gcc/testsuite/gcc.target/sparc/pr105573.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
> create mode 100644 gcc/testsuite/gcc.target/sparc/pr105573.c
>
> diff --git a/gcc/testsuite/gcc.target/sparc/pr105573.c b/gcc/testsuite/gcc.target/sparc/pr105573.c
> new file mode 100644
> index 00000000000..9eba2e4beba
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/sparc/pr105573.c
> @@ -0,0 +1,14 @@
> +/* { dg-do compile } */
> +/* { dg-options "-O2 -mvis3" } */
> +
> +int *UINT_sign_args, UINT_sign_steps;
> +int *UINT_sign_ip1;
> +__attribute__((optimize("O3"))) void UINT_sign() {
is the optimize attribute necessary or does -O3 -mvis3 also reproduce
the issue?
> + char *op1 = (char*) UINT_sign_args;
> + int os1 = UINT_sign_steps, i;
> + for (; i; i++, op1 += os1) {
> + unsigned in = *(unsigned *)UINT_sign_ip1;
> + int *out = (int*) op1;
> + *out = in > 0;
> + }
> +}
next prev parent reply other threads:[~2023-04-24 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 19:33 Sam James
2023-04-24 7:36 ` Richard Biener [this message]
2023-04-24 22:29 ` Sam James
2023-04-24 22:30 ` [PATCH v2] " Sam James
2023-04-25 6:21 ` Richard Biener
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=nycvar.YFH.7.77.849.2304240735350.4466@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gcc.gnu.org \
--cc=rguenth@gcc.gnu.org \
--cc=sam@gentoo.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).