public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/55876] internal compiler error: in gen_rtx_SUBREG, at emit-rtl.c:776 Date: Fri, 04 Jan 2013 16:00:00 -0000 [thread overview] Message-ID: <bug-55876-4-sMpdZPoFLp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55876-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55876 --- Comment #2 from vries at gcc dot gnu.org 2013-01-04 16:00:07 UTC --- This patch introduces an assert that triggers before rather than during gen_rtx_SUBREG: ... Index: optabs.c =================================================================== --- optabs.c (revision 194898) +++ optabs.c (working copy) @@ -330,7 +330,12 @@ widen_operand (rtx op, enum machine_mode /* If MODE is no wider than a single word, we return a paradoxical SUBREG. */ if (GET_MODE_SIZE (mode) <= UNITS_PER_WORD) - return gen_rtx_SUBREG (mode, force_reg (GET_MODE (op), op), 0); + { + /* Check that the result is a paradoxical subreg (outer mode strictly + larger than inner mode. */ + gcc_assert (GET_MODE_SIZE (mode) > GET_MODE_SIZE (GET_MODE (op))); + return gen_rtx_SUBREG (mode, force_reg (GET_MODE (op), op), 0); + } /* Otherwise, get an object of MODE, clobber it, and set the low-order part to OP. */ ... This assert allows triggers both with -EB and -EL, while the original assert only triggers with -EB.
next prev parent reply other threads:[~2013-01-04 16:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-04 15:12 [Bug target/55876] New: " vries at gcc dot gnu.org 2013-01-04 15:23 ` [Bug target/55876] " vries at gcc dot gnu.org 2013-01-04 16:00 ` vries at gcc dot gnu.org [this message] 2013-01-04 16:43 ` vries at gcc dot gnu.org 2013-01-07 10:21 ` vries at gcc dot gnu.org 2013-01-15 17:25 ` vries at gcc dot gnu.org 2013-05-25 8:29 ` rsandifo at gcc dot gnu.org 2013-05-25 8:42 ` vries 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-55876-4-sMpdZPoFLp@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).