From: Richard Biener <rguenther@suse.de>
To: Tamar Christina <tamar.christina@arm.com>
Cc: gcc-patches@gcc.gnu.org, nd@arm.com, jlaw@ventanamicro.com
Subject: Re: [PATCH]middle-end: add additional runtime test for [PR113467]
Date: Mon, 5 Feb 2024 14:11:19 +0100 (CET) [thread overview]
Message-ID: <9oop2600-9576-220o-oq8p-pqq8ss4p89q7@fhfr.qr> (raw)
In-Reply-To: <patch-18246-tamar@arm.com>
On Mon, 5 Feb 2024, Tamar Christina wrote:
> Hi All,
>
> This just adds an additional runtime testcase for the fixed issue.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu and no issues.
>
> Ok for master?
I think you need a lp64 target check for the large constants or
alternatively use uint64_t?
> Thanks,
> Tamar
>
> gcc/testsuite/ChangeLog:
>
> PR tree-optimization/113467
> * gcc.dg/vect/vect-early-break_110-pr113467.c: New test.
>
> --- inline copy of patch --
> diff --git a/gcc/testsuite/gcc.dg/vect/vect-early-break_110-pr113467.c b/gcc/testsuite/gcc.dg/vect/vect-early-break_110-pr113467.c
> new file mode 100644
> index 0000000000000000000000000000000000000000..2d8a071c0e922ccfd5fa8c7b27044444852dbd95
> --- /dev/null
> +++ b/gcc/testsuite/gcc.dg/vect/vect-early-break_110-pr113467.c
> @@ -0,0 +1,51 @@
> +/* { dg-add-options vect_early_break } */
> +/* { dg-require-effective-target vect_early_break } */
> +/* { dg-require-effective-target vect_int } */
> +
> +/* { dg-final { scan-tree-dump-not "LOOP VECTORIZED" "vect" } } */
> +
> +#include "tree-vect.h"
> +
> +typedef struct gcry_mpi *gcry_mpi_t;
> +struct gcry_mpi {
> + int nlimbs;
> + unsigned long *d;
> +};
> +
> +long gcry_mpi_add_ui_up;
> +void gcry_mpi_add_ui(gcry_mpi_t w, gcry_mpi_t u, unsigned v) {
> + gcry_mpi_add_ui_up = *w->d;
> + if (u) {
> + unsigned long *res_ptr = w->d, *s1_ptr = w->d;
> + int s1_size = u->nlimbs;
> + unsigned s2_limb = v, x = *s1_ptr++;
> + s2_limb += x;
> + *res_ptr++ = s2_limb;
> + if (x)
> + while (--s1_size) {
> + x = *s1_ptr++ + 1;
> + *res_ptr++ = x;
> + if (x) {
> + break;
> + }
> + }
> + }
> +}
> +
> +int main()
> +{
> + check_vect ();
> +
> + static struct gcry_mpi sv;
> + static unsigned long vals[] = {4294967288, 191, 4160749568, 4294963263,
> + 127, 4294950912, 255, 4294901760,
> + 534781951, 33546240, 4294967292, 4294960127,
> + 4292872191, 4294967295, 4294443007, 3};
> + gcry_mpi_t v = &sv;
> + v->nlimbs = 16;
> + v->d = vals;
> +
> + gcry_mpi_add_ui(v, v, 8);
> + if (v->d[1] != 192)
> + __builtin_abort();
> +}
>
>
>
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH,
Frankenstrasse 146, 90461 Nuernberg, Germany;
GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
next prev parent reply other threads:[~2024-02-05 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 13:08 Tamar Christina
2024-02-05 13:11 ` Richard Biener [this message]
2024-02-05 13:35 ` Tamar Christina
2024-02-05 14:29 ` 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=9oop2600-9576-220o-oq8p-pqq8ss4p89q7@fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.com \
--cc=nd@arm.com \
--cc=tamar.christina@arm.com \
/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).