public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/21518] [4.0/4.1 Regression] error: unable to find a register to spill in class 'Q_REGS' with -fPIC and -O2
Date: Wed, 11 May 2005 21:23:00 -0000	[thread overview]
Message-ID: <20050511212310.3534.qmail@sourceware.org> (raw)
In-Reply-To: <20050511195406.21518.couriousous@mandriva.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-11 21:23 -------
Confirmed, here is a testcase for before 4.0.0, if you use this testcase after 4.0.0, use -fno-tree-pre 
but that is because we missing a PRE opportunity right now (PR 21520) and if that gets fixed, the 
orginal testcase will not ICE any more:
static void __attribute__((regparm(3)))
drawPointsLines (char type, int first, int *dd) {*dd += 1;}

int do_locator (int *call)
{
  char prephitmp5;
  int type;
  int i;

  if (call == 0) {prephitmp5 = 1;}
  else
  {

  type = *call;
  i = 0;

do {
  if (i != type)
    drawPointsLines ((int) (char) type, 0, call);
  i = i + 1;
  } while (i != 2);
  
  prephitmp5 = (char) type;
}
  drawPointsLines ((int) prephitmp5, 0, call);
  return 0;
}


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
      Known to work|3.4.0                       |
   Last reconfirmed|0000-00-00 00:00:00         |2005-05-11 21:23:09
               date|                            |


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


  parent reply	other threads:[~2005-05-11 21:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 19:54 [Bug c/21518] New: " couriousous at mandriva dot org
2005-05-11 19:57 ` [Bug target/21518] " pinskia at gcc dot gnu dot org
2005-05-11 21:00 ` [Bug target/21518] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-05-11 21:23 ` pinskia at gcc dot gnu dot org [this message]
2005-05-11 21:24 ` pinskia at gcc dot gnu dot org
2005-05-12  8:59 ` jakub at gcc dot gnu dot org
2005-05-12 10:59 ` [Bug target/21518] " steven at gcc dot gnu dot org
2005-05-12 12:00 ` [Bug target/21518] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-05-12 12:02 ` pinskia at gcc dot gnu dot org
2005-07-06 17:03 ` mmitchel at gcc dot gnu dot org
2005-07-26 23:38 ` steven at gcc dot gnu dot org
2005-09-27 16:20 ` mmitchel 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=20050511212310.3534.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: 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).