public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66747] [6 Regression] The commit r225260 broke the builds of the mips-{mti,img}-linux-gnu tool chains.
Date: Fri, 03 Jul 2015 10:06:00 -0000	[thread overview]
Message-ID: <bug-66747-4-bBomxVFGKn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66747-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66747

--- Comment #2 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
get_attr_got fails when called with a SEQUENCE.
I am not sure if reg_overlap_mentioned_p works with SEQUENCE.


--- gcc/config/mips/mips.c.jj   2015-06-08 23:06:50.000000000 +0200
+++ gcc/config/mips/mips.c      2015-07-03 11:38:48.962336295 +0200
@@ -9902,7 +9902,7 @@ mips_cfun_has_inflexible_gp_ref_p (void)
 static bool
 mips_insn_has_flexible_gp_ref_p (rtx_insn *insn)
 {
-  return (get_attr_got (insn) != GOT_UNSET
+  return ((PATTERN (insn)->code != SEQUENCE && get_attr_got (insn) !=
GOT_UNSET)
          || mips_small_data_pattern_p (PATTERN (insn))
          || reg_overlap_mentioned_p (pic_offset_table_rtx, PATTERN (insn)));
 }


  parent reply	other threads:[~2015-07-03 10:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  1:04 [Bug c/66747] New: " doug.gilmore at imgtec dot com
2015-07-03  8:00 ` [Bug middle-end/66747] [5/6 Regression] " rguenth at gcc dot gnu.org
2015-07-03  8:21 ` [Bug middle-end/66747] [6 " edlinger at gcc dot gnu.org
2015-07-03 10:06 ` edlinger at gcc dot gnu.org [this message]
2015-07-03 11:23 ` bernd.edlinger at hotmail dot de
2015-07-03 20:42 ` doug.gilmore at imgtec dot com
2015-07-04  3:44 ` doug.gilmore at imgtec dot com
2015-07-04  7:50 ` [Bug target/66747] " edlinger at gcc dot gnu.org
2015-07-04 19:02 ` edlinger at gcc dot gnu.org
2015-07-06 20:32 ` doug.gilmore 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-66747-4-bBomxVFGKn@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: link
Be 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).