public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/106449] ICE in #pragma omp parallel for simd since r6-4544-ge01d41e553aae245
Date: Wed, 27 Jul 2022 14:35:29 +0000 [thread overview]
Message-ID: <bug-106449-4-96QruapWwr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106449-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106449
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Comment on attachment 53362
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53362
gcc13-pr106449.patch
> + t = fold_convert (sizetype, fd->loops[i + 1].n1);
> + t = fold_build_pointer_plus (t2, t);
I think the first line is not needed, given that fold_build_pointer_plus_loc
has:
return fold_build2_loc (loc, POINTER_PLUS_EXPR, TREE_TYPE (ptr),
ptr, convert_to_ptrofftype_loc (loc, off));
and the convert_to_ptrofftype_loc does:
if (ptrofftype_p (TREE_TYPE (off)))
return off;
return fold_convert_loc (loc, sizetype, off);
where the last line matches your first line. Hence, just calling
t = fold_build_pointer_plus (t2, fd->loops[i + 1].n1);
should gives the same result and is more compact (avoids a line and a
2-character indent).
next prev parent reply other threads:[~2022-07-27 14:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 16:10 [Bug middle-end/106449] New: ICE in #pragma omp parallel for simd sandra at gcc dot gnu.org
2022-07-26 19:46 ` [Bug middle-end/106449] " burnus at gcc dot gnu.org
2022-07-27 7:10 ` rguenth at gcc dot gnu.org
2022-07-27 8:35 ` [Bug middle-end/106449] ICE in #pragma omp parallel for simd since r6-4544-ge01d41e553aae245 marxin at gcc dot gnu.org
2022-07-27 11:05 ` jakub at gcc dot gnu.org
2022-07-27 12:19 ` jakub at gcc dot gnu.org
2022-07-27 14:07 ` jakub at gcc dot gnu.org
2022-07-27 14:35 ` burnus at gcc dot gnu.org [this message]
2022-07-27 15:26 ` burnus at gcc dot gnu.org
2022-07-28 10:11 ` jakub at gcc dot gnu.org
2022-07-28 10:12 ` jakub at gcc dot gnu.org
2022-07-29 7:54 ` cvs-commit at gcc dot gnu.org
2022-07-29 8:06 ` jakub at gcc dot gnu.org
2022-07-30 9:34 ` cvs-commit at gcc dot gnu.org
2022-07-30 10:09 ` jakub at gcc dot gnu.org
2022-11-03 14:09 ` jakub at gcc dot gnu.org
2022-11-28 22:08 ` pinskia at gcc dot gnu.org
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=bug-106449-4-96QruapWwr@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).