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/96730] [10/11 Regression] ICE on x86_64-linux-gnu with `-O1` to `-O3` (in verify_sra_access_forest, at tree-sra.c:2352) since r10-6320-g5b9e89c922dc2e7e Date: Tue, 25 Aug 2020 14:12:44 +0000 [thread overview] Message-ID: <bug-96730-4-EDaKSV7oTL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96730-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96730 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:e57cdbca52df908a48bbf92c64d50dd46f483de9 commit r10-8661-ge57cdbca52df908a48bbf92c64d50dd46f483de9 Author: Martin Jambor <mjambor@suse.cz> Date: Tue Aug 25 16:11:56 2020 +0200 sra: Bail out when encountering accesses with negative offsets (PR 96730) I must admit I was quite surprised to see that SRA does not disqualify an aggregate from any transformations when it encounters an offset for which get_ref_base_and_extent returns a negative offset. It may not matter too much because I sure hope such programs always have undefined behavior (SRA candidates are local variables on stack) but it is probably better not to perform weird transformations on them as build ref model with the new build_reconstructed_reference function currently happily do for negative offsets (they just copy the existing expression which is then used as the expression of a "propagated" access) and of course the compiler must not ICE (as it currently does because the SRA forest verifier does not like the expression). gcc/ChangeLog: 2020-08-24 Martin Jambor <mjambor@suse.cz> PR tree-optimization/96730 * tree-sra.c (create_access): Disqualify any aggregate with negative offset access. (build_ref_for_model): Add assert that offset is non-negative. gcc/testsuite/ChangeLog: 2020-08-24 Martin Jambor <mjambor@suse.cz> PR tree-optimization/96730 * gcc.dg/tree-ssa/pr96730.c: New test. (cherry picked from commit 556600286dd312d3ddf3d673a8579576862663e3)
next prev parent reply other threads:[~2020-08-25 14:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-21 3:33 [Bug tree-optimization/96730] New: ICE on x86_64-linux-gnu with `-O1` to `-O3` (in verify_sra_access_forest, at tree-sra.c:2352) cnsun at uwaterloo dot ca 2020-08-24 8:18 ` [Bug tree-optimization/96730] [10/11 Regression] ICE on x86_64-linux-gnu with `-O1` to `-O3` (in verify_sra_access_forest, at tree-sra.c:2352) since r10-6320-g5b9e89c922dc2e7e marxin at gcc dot gnu.org 2020-08-24 9:50 ` jamborm at gcc dot gnu.org 2020-08-24 15:09 ` jamborm at gcc dot gnu.org 2020-08-25 11:19 ` rguenth at gcc dot gnu.org 2020-08-25 11:34 ` cvs-commit at gcc dot gnu.org 2020-08-25 14:12 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-25 14:15 ` jamborm 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-96730-4-EDaKSV7oTL@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).