public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/95108] [9 Regression] ICE in tree_fits_uhwi_p, at tree.c:7292 Date: Wed, 16 Sep 2020 19:22:12 +0000 [thread overview] Message-ID: <bug-95108-4-ROLhUVAqu5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95108-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95108 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:b78ea59edbd354fed914d0f8eb78109db7316ce8 commit r9-8899-gb78ea59edbd354fed914d0f8eb78109db7316ce8 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu May 14 09:51:05 2020 +0200 openmp: Fix placement of 2nd+ preparation statement for PHIs in simd clone lowering [PR95108] For normal stmts, preparation statements are inserted before the stmt, so if we need multiple, they are in the correct order, but for PHIs we emit them after labels in the entry successor bb, and we used to emit them in the reverse order that way. 2020-05-14 Jakub Jelinek <jakub@redhat.com> PR middle-end/95108 * omp-simd-clone.c (struct modify_stmt_info): Add after_stmt member. (ipa_simd_modify_stmt_ops): For PHIs, only add before first stmt in entry block if info->after_stmt is NULL, otherwise add after that stmt and update it after adding each stmt. (ipa_simd_modify_function_body): Initialize info.after_stmt. * gcc.dg/gomp/pr95108.c: New test. (cherry picked from commit d0fb9ffc1b8f3b86bbdf0e915cec2136141b329b)
next prev parent reply other threads:[~2020-09-16 19:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-13 16:24 [Bug c/95108] New: [10/11 " gscfq@t-online.de 2020-05-13 17:46 ` [Bug c/95108] [9/10/11 " jakub at gcc dot gnu.org 2020-05-13 18:54 ` [Bug middle-end/95108] " jakub at gcc dot gnu.org 2020-05-14 6:16 ` rguenth at gcc dot gnu.org 2020-05-14 7:53 ` cvs-commit at gcc dot gnu.org 2020-05-14 8:07 ` [Bug middle-end/95108] [9/10 " jakub at gcc dot gnu.org 2020-06-14 10:07 ` cvs-commit at gcc dot gnu.org 2020-06-14 11:47 ` [Bug middle-end/95108] [9 " jakub at gcc dot gnu.org 2020-09-16 19:22 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-17 17:51 ` jakub 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-95108-4-ROLhUVAqu5@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: linkBe 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).