From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roger Sayle <roger@nextmovesoftware.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-chrec: Fix up ICE on pointer multiplication [PR107835]
Date: Wed, 30 Nov 2022 10:10:09 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2211301010030.7009@jbgna.fhfr.qr> (raw)
In-Reply-To: <Y4cmlqFFMt3p7Nz8@tucnak>
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
On Wed, 30 Nov 2022, Jakub Jelinek wrote:
> Hi!
>
> r13-254-gdd3c7873a61019e9 added an optimization for {a, +, a} (x-1),
> but as can be seen on the following testcase, the way it is written
> where chrec_fold_multiply is called with type doesn't work for pointers:
> res = build_int_cst (TREE_TYPE (x), 1);
> res = chrec_fold_plus (TREE_TYPE (x), x, res);
> res = chrec_convert_rhs (type, res, NULL);
> res = chrec_fold_multiply (type, chrecr, res);
> while what we were doing before and what is still used if the condition
> doesn't match is fine:
> res = chrec_convert_rhs (TREE_TYPE (chrecr), x, NULL);
> res = chrec_fold_multiply (TREE_TYPE (chrecr), chrecr, res);
> res = chrec_fold_plus (type, CHREC_LEFT (chrec), res);
> because it performs chrec_fold_multiply on TREE_TYPE (chrecr) and converts
> only afterwards.
>
> I think the easiest fix is to ignore the new path for pointer types.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
OK.
Thanks,
Richard.
> 2022-11-30 Jakub Jelinek <jakub@redhat.com>
>
> PR tree-optimization/107835
> * tree-chrec.cc (chrec_apply): Don't handle "{a, +, a} (x-1)"
> as "a*x" if type is a pointer type.
>
> * gcc.c-torture/compile/pr107835.c: New test.
>
> --- gcc/tree-chrec.cc.jj 2022-05-10 18:33:14.641029951 +0200
> +++ gcc/tree-chrec.cc 2022-11-29 15:24:41.810400368 +0100
> @@ -622,7 +622,8 @@ chrec_apply (unsigned var,
> /* "{a, +, b} (x)" -> "a + b*x". */
> else if (operand_equal_p (CHREC_LEFT (chrec), chrecr)
> && TREE_CODE (x) == PLUS_EXPR
> - && integer_all_onesp (TREE_OPERAND (x, 1)))
> + && integer_all_onesp (TREE_OPERAND (x, 1))
> + && !POINTER_TYPE_P (type))
> {
> /* We know the number of iterations can't be negative.
> So {a, +, a} (x-1) -> "a*x". */
> --- gcc/testsuite/gcc.c-torture/compile/pr107835.c.jj 2022-11-29 15:31:32.565382590 +0100
> +++ gcc/testsuite/gcc.c-torture/compile/pr107835.c 2022-11-29 15:31:15.795628304 +0100
> @@ -0,0 +1,11 @@
> +/* PR tree-optimization/107835 */
> +
> +int *
> +foo (void)
> +{
> + int *x = 0;
> + unsigned n = n;
> + for (; n; --n, ++x)
> + ;
> + return x;
> +}
>
> Jakub
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)
prev parent reply other threads:[~2022-11-30 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 9:47 Jakub Jelinek
2022-11-30 10:10 ` Richard Biener [this message]
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.2211301010030.7009@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=roger@nextmovesoftware.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).