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 target/100106] [10 Regression] ICE in gen_movdi, at config/arm/arm.md:6187 since r10-2840-g70cdb21e Date: Thu, 25 May 2023 02:46:19 +0000 [thread overview] Message-ID: <bug-100106-4-eBZeT3QqHw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100106-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100106 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:d6b756447cd58bcca20e6892790582308b869817 commit r14-1187-gd6b756447cd58bcca20e6892790582308b869817 Author: Alexandre Oliva <oliva@adacore.com> Date: Wed May 24 03:07:56 2023 -0300 [PR100106] Reject unaligned subregs when strict alignment is required The testcase for pr100106, compiled with optimization for 32-bit powerpc -mcpu=604 with -mstrict-align expands the initialization of a union from a float _Complex value into a load from an SCmode constant pool entry, aligned to 4 bytes, into a DImode pseudo, requiring 8-byte alignment. The patch that introduced the testcase modified simplify_subreg to avoid changing the MEM to outermode, but simplify_gen_subreg still creates a SUBREG or a MEM that would require stricter alignment than MEM's, and lra_constraints appears to get confused by that, repeatedly creating unsatisfiable reloads for the SUBREG until it exceeds the insn count. Avoiding the unaligned SUBREG, expand splits the DImode dest into SUBREGs and loads each SImode word of the constant pool with the proper alignment. for gcc/ChangeLog PR target/100106 * emit-rtl.cc (validate_subreg): Reject a SUBREG of a MEM that requires stricter alignment than MEM's. for gcc/testsuite/ChangeLog PR target/100106 * gcc.target/powerpc/pr100106-sa.c: New.
next prev parent reply other threads:[~2023-05-25 2:46 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 21:06 [Bug target/100106] New: [10/11 " acoplan at gcc dot gnu.org 2021-04-15 21:06 ` [Bug target/100106] " acoplan at gcc dot gnu.org 2021-04-16 7:09 ` rguenth at gcc dot gnu.org 2021-04-16 7:13 ` rguenth at gcc dot gnu.org 2021-04-20 6:00 ` bernd.edlinger at hotmail dot de 2021-04-27 15:48 ` [Bug target/100106] [10/11/12 " cvs-commit at gcc dot gnu.org 2021-04-27 15:51 ` [Bug target/100106] [10/11 " edlinger at gcc dot gnu.org 2021-07-19 11:59 ` rguenth at gcc dot gnu.org 2022-04-07 10:39 ` cvs-commit at gcc dot gnu.org 2022-04-08 10:20 ` [Bug target/100106] [10 " rearnsha at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-05-25 2:46 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-07 9:35 ` 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-100106-4-eBZeT3QqHw@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).