public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/34641] [4.3 Regression] ICE in reload_cse_simplify_operands, at postreload.c:395 Date: Mon, 07 Jan 2008 17:41:00 -0000 [thread overview] Message-ID: <20080107172830.8427.qmail@sourceware.org> (raw) In-Reply-To: <bug-34641-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from krebbel at gcc dot gnu dot org 2008-01-07 17:28 ------- The (const_int 3148725999 [0xbbadbeef]) is accepted by legitimate_constant_p since it is expected to end up in the literal pool. But in this case the constant becomes part of a REG_EQUIV note of an insn moving the constant into a pseudo register. Generating a reload for a later insn using the pseudo as memory base register the REG_EQUIV note is used by push_reload to replace the pseudo directly with the constant. The emitted move insn can't be recognized since none of the constraints of the move pattern accepts the large constant. I think push_reload has to make sure that the move pattern to be emitted is able to deal with the constant taken from the reg_equiv_constant array. -- krebbel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2008-01-07 17:28:30 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34641
next prev parent reply other threads:[~2008-01-07 17:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-02 16:17 [Bug target/34641] New: " rguenth at gcc dot gnu dot org 2008-01-02 16:53 ` [Bug target/34641] " rguenth at gcc dot gnu dot org 2008-01-03 10:35 ` rguenth at gcc dot gnu dot org 2008-01-07 17:41 ` krebbel at gcc dot gnu dot org [this message] 2008-01-10 17:40 ` krebbel at gcc dot gnu dot org 2008-01-11 3:58 ` ismail at pardus dot org dot tr 2008-01-11 9:36 ` krebbel at gcc dot gnu dot org 2008-05-26 19:26 ` pinskia at gcc dot gnu dot 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=20080107172830.8427.qmail@sourceware.org \ --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).