public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/59317] [4.9 Regression] [LRA,MIPS] ICE: in check_rtl, at lra.c (insn does not satisfy constraints) Date: Tue, 03 Dec 2013 23:08:00 -0000 [thread overview] Message-ID: <bug-59317-4-4mLvPzGvwK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59317-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59317 Vladimir Makarov <vmakarov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org --- Comment #1 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- (In reply to Robert Suchanek from comment #0) > > The LRA generates the following piece of RTL that fails at check_rtl(): > > (insn 265 54 267 2 (set (reg:SI 8 $8 [339]) > (const:SI (unspec:SI [ > (const_int 0 [0]) > ] UNSPEC_GP))) ia64-1_testcase.c:49 295 {*movsi_mips16} > (nil)) > > This does not satisfy the operand’s constrains in mov<mode>_mips16 pattern. > > The ICE appears to be triggered because of ALL_REGS assigned to new pseudos > generated and the pseudo data gets expanded but I do not know how to fix it > without breaking PR59133 again. I believe it has been solved by one of the latest patches. The pseudos with ALL_REGS are really generated but their class is changed lately. It would be nice, Robert, if you check this and close the PR. >From gcc-bugs-return-436585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 03 23:09:21 2013 Return-Path: <gcc-bugs-return-436585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18866 invoked by alias); 3 Dec 2013 23:09:21 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 18729 invoked by uid 48); 3 Dec 2013 23:08:47 -0000 From: "macro@linux-mips.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59371] [4.8/4.9 Regression] Performance regression in GCC 4.8 and later versions. Date: Tue, 03 Dec 2013 23:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: macro@linux-mips.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-59371-4-HuNDI2jz7l@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59371-4@http.gcc.gnu.org/bugzilla/> References: <bug-59371-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg00240.txt.bz2 Content-length: 1338 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY371 Maciej W. Rozycki <macro@linux-mips.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro@linux-mips.org --- Comment #3 from Maciej W. Rozycki <macro@linux-mips.org> --- Caused by: ------------------------------------------------------------------------ r193882 | rguenth | 2012-11-28 09:27:10 +0000 (Wed, 28 Nov 2012) | 19 lines 2012-11-28 Richard Biener <rguenther@suse.de> PR c/35634 * gimple.h (gimplify_self_mod_expr): Declare. * gimplify.c (gimplify_self_mod_expr): Export. Take a different type for performing the arithmetic in. (gimplify_expr): Adjust. * tree-vect-loop-manip.c (vect_can_advance_ivs_p): Strip sign conversions we can re-apply after adjusting the IV. c-family/ * c-gimplify.c (c_gimplify_expr): Gimplify self-modify expressions here and use a type with proper overflow behavior for types that would need to be promoted for the arithmetic. * gcc.dg/torture/pr35634.c: New testcase. * g++.dg/torture/pr35634.C: Likewise. * gcc.dg/vect/pr18536.c: Mark worker function noinline. ------------------------------------------------------------------------
next prev parent reply other threads:[~2013-12-03 23:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-27 16:14 [Bug rtl-optimization/59317] New: " robert.suchanek at imgtec dot com 2013-11-28 11:38 ` [Bug rtl-optimization/59317] " rguenth at gcc dot gnu.org 2013-12-03 23:08 ` vmakarov at gcc dot gnu.org [this message] 2013-12-04 12:02 ` robert.suchanek at imgtec dot com 2013-12-04 16:13 ` vmakarov at gcc dot gnu.org 2013-12-05 10:06 ` robert.suchanek at imgtec dot com 2013-12-05 10:08 ` robert.suchanek at imgtec dot com 2013-12-05 19:39 ` vmakarov at gcc dot gnu.org 2013-12-06 9:41 ` robert.suchanek at imgtec dot com
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-59317-4-4mLvPzGvwK@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).