public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60851] [4.9/4.10 Regression] ICE: in extract_constrain_insn_cached, at recog.c:2117 with -flive-range-shrinkage -mdispatch-scheduler -march=bdver4 Date: Wed, 16 Apr 2014 13:02:00 -0000 [thread overview] Message-ID: <bug-60851-4-9Nodtvae1Y@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60851-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60851 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- constraint_operands before reload doesn't accept a pseudo for "m" constraint, only during reload: /* Before reload, accept what reload can turn into mem. */ else if (strict < 0 && CONSTANT_P (op)) win = 1; /* During reload, accept a pseudo */ else if (reload_in_progress && REG_P (op) && REGNO (op) >= FIRST_PSEUDO_REGISTER) win = 1; Wonder if it would be ok to change that reload_in_progress to !reload_completed or !strict or something similar, or, if not, whether we shouldn't have some other memory constraint on i?86 or everywhere that would be accept a pseudo for strict < 0 instead of only for reload_in_progress.
next prev parent reply other threads:[~2014-04-16 13:02 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-15 19:15 [Bug target/60851] New: " zsojka at seznam dot cz 2014-04-16 9:03 ` [Bug target/60851] [4.9/4.10 Regression] " jakub at gcc dot gnu.org 2014-04-16 13:02 ` jakub at gcc dot gnu.org [this message] 2014-04-16 14:58 ` rth at gcc dot gnu.org 2014-04-18 7:03 ` zsojka at seznam dot cz 2014-04-22 11:35 ` jakub at gcc dot gnu.org 2014-06-26 13:00 ` rguenth at gcc dot gnu.org 2014-07-16 13:27 ` jakub at gcc dot gnu.org 2014-10-30 10:37 ` [Bug target/60851] [4.9/5 " jakub at gcc dot gnu.org 2015-02-24 11:19 ` jakub at gcc dot gnu.org 2015-03-19 7:30 ` [Bug rtl-optimization/60851] " ubizjak at gmail dot com 2015-03-20 8:32 ` uros at gcc dot gnu.org 2015-03-22 20:16 ` [Bug rtl-optimization/60851] [4.9 " ubizjak at gmail dot com 2015-03-22 21:11 ` ubizjak at gmail dot com 2015-03-23 16:14 ` rth at gcc dot gnu.org 2015-03-24 7:50 ` uros at gcc dot gnu.org 2015-03-24 8:13 ` ubizjak at gmail 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-60851-4-9Nodtvae1Y@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).