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 target/54338] internal compiler error: in find_costs_and_classes, at ira-costs.c:1711
Date: Fri, 31 Aug 2012 18:35:00 -0000	[thread overview]
Message-ID: <bug-54338-4-1np2QmDIzv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54338-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54338

--- Comment #2 from Vladimir Makarov <vmakarov at gcc dot gnu.org> 2012-08-31 18:35:17 UTC ---
IRA can not find super set of GENERAL_REGS and IWMMXT_GR_REGS.  It should not
happen as ALL_REGS exits as the last resort for this.

GCC documentation contains

@findex ALL_REGS
@findex NO_REGS
In general, each register will belong to several classes.  In fact, one
class must be named @code{ALL_REGS} and contain all the registers.  Another
class must be named @code{NO_REGS} and contain no registers.  Often the
union of two classes will be another class; however, this is not required.

Unfortunately, for some reasons ALL_REGS for ARM port does not contain
IWMMXT_GR_REGS, CC_REG, VFPCC_REG, SFP_REG, and AFP_REG.

I think ARM ALL_REGS should contain really all regs.  If this is not possible
for some reasons, we should fix the documentation and I should make a patch for
IRA fixing it in another way.  But I think the right solution would be fixing
ARM ALL_REGS definition (also probably the right cost should be returned by ARM
targets for different combinations of reg classes).


  parent reply	other threads:[~2012-08-31 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  1:37 [Bug c/54338] New: " xyqi at marvell dot com
2012-08-21  1:39 ` [Bug c/54338] " xyqi at marvell dot com
2012-08-31 18:35 ` vmakarov at gcc dot gnu.org [this message]
2012-09-26 22:57 ` [Bug target/54338] " janis at gcc dot gnu.org
2013-01-10  0:14 ` janis at gcc dot gnu.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=bug-54338-4-1np2QmDIzv@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).