public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/20928] [4.0/4.1 regression] ICE: unrecognizable insns with -fPIC -O1 Date: Sun, 30 Oct 2005 18:01:00 -0000 [thread overview] Message-ID: <20051030180009.32473.qmail@sourceware.org> (raw) In-Reply-To: <bug-20928-260@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from hubicka at gcc dot gnu dot org 2005-10-30 18:00 ------- testing fix that should make legitimize_pic_address correctly decompose the address. Similar to Steven's but I think it actually works ;) Index: config/i386/i386.c =================================================================== --- config/i386/i386.c (revision 106026) +++ config/i386/i386.c (working copy) @@ -6016,7 +6016,18 @@ legitimize_pic_address (rtx orig, rtx re } else { - if (GET_CODE (addr) == CONST) + if (GET_CODE (addr) == CONST_INT + && !x86_64_immediate_operand (addr, VOIDmode)) + { + if (reg) + { + emit_move_insn (reg, addr); + new = reg; + } + else + new = force_reg (DImode, addr); + } + else if (GET_CODE (addr) == CONST) { addr = XEXP (addr, 0); -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20928
next prev parent reply other threads:[~2005-10-30 18:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20928-260@http.gcc.gnu.org/bugzilla/> 2005-10-10 3:20 ` [Bug target/20928] [4.0/4.1 regression] ICE: unrecognizable insns kazu at gcc dot gnu dot org 2005-10-13 16:03 ` pinskia at gcc dot gnu dot org 2005-10-19 13:51 ` [Bug target/20928] [4.0/4.1 regression] ICE: unrecognizable insns with -fPIC -O1 pluto at agmk dot net 2005-10-19 14:02 ` pinskia at gcc dot gnu dot org 2005-10-30 18:01 ` hubicka at gcc dot gnu dot org [this message] 2005-10-31 3:06 ` mmitchel at gcc dot gnu dot org 2005-10-31 17:14 ` steven at gcc dot gnu dot org 2005-10-31 17:16 ` pinskia at gcc dot gnu dot org 2005-10-31 18:46 ` hubicka 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=20051030180009.32473.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).