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 tree-optimization/94574] aarch64: ICE during GIMPLE pass:ccp Date: Tue, 14 Apr 2020 14:01:21 +0000 [thread overview] Message-ID: <bug-94574-4-4wkWOuNAuD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94574-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94574 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:f65cecabc32fe12b024253502af953e657e1a878 commit r10-7716-gf65cecabc32fe12b024253502af953e657e1a878 Author: Yang Yang <yangyang305@huawei.com> Date: Tue Apr 14 19:42:23 2020 +0000 PR tree-optimization/94574 - aarch64: ICE during GIMPLE pass:ccp In this PR the testcase ICEs because a BIT_INSERT_EXPR whose replaced bits are not fully inside the container is generated. A size check is added to avoid this kind of ICE. gcc/ChangeLog: PR tree-optimization/94574 * tree-ssa.c (non_rewritable_lvalue_p): Add size check when analyzing whether a vector-insert is rewritable using a BIT_INSERT_EXPR. gcc/testsuite/ChangeLog: PR tree-optimization/94574 * gcc.dg/pr94574.c: New test.
next prev parent reply other threads:[~2020-04-14 14:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-13 8:50 [Bug tree-optimization/94574] New: " yangyang305 at huawei dot com 2020-04-13 9:24 ` [Bug tree-optimization/94574] " yangyang305 at huawei dot com 2020-04-13 10:00 ` yangyang305 at huawei dot com 2020-04-14 6:37 ` marxin at gcc dot gnu.org 2020-04-14 6:37 ` marxin at gcc dot gnu.org 2020-04-14 14:01 ` cvs-commit at gcc dot gnu.org [this message] 2020-04-14 14:02 ` rguenth 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-94574-4-4wkWOuNAuD@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).