public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guptan at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/21616] [3.4 only] ICE: unable to find a register to spill in class `FLOAT_REGS'
Date: Sat, 21 May 2005 00:28:00 -0000	[thread overview]
Message-ID: <20050521002818.30991.qmail@sourceware.org> (raw)
In-Reply-To: <20050517083823.21616.raj.khem@gmail.com>


------- Additional Comments From guptan at hotmail dot com  2005-05-21 00:28 -------
Thanks Andrew.

[17:00] <ngupta> pinskia, yes I am trying to get an answer if PR21616 existed on
gcc-4.0 :)
[17:01] <pinskia> it might be worked around by optimizing it better :)
[17:01] <ngupta> I suspect its already fixed in rs6000.md, but dont want to go
over the whole setup thingie
[17:02] <pinskia> let me try it
[17:02] <ngupta> than I rather backport that from gcc-4.0
[17:05] <pinskia> did you try the patch for PR 15286?
[17:07] <ngupta> nope, lemme look
[17:08] <pinskia> oh, that will not help
[17:08] <pinskia> I know which bug this is, it has to do with ld not taking any
old offset but only aligned offsets
[17:08] <pinskia> let me find that patch
[17:08] <-- rosalesa has quit ("Leaving")
[17:13] <ngupta> oh ok, i m waiting
[17:14] --> jk- (~jk@toolbox.otago.ac.nz) has joined #ppc64
[17:14] <pinskia> ngupta: the patch for PR 13674 is the one which really fixed
the problem I think
[17:15] <pinskia> there is a workaround on the 3.4 branch for PR 13674 but it
looks like it does not work for this testcase :(
[17:16] <ngupta> yup, thats what I was abt to try
[17:16] <ngupta> -fnew-ra
[17:17] <pinskia> in fact I think the work around is causing the ICE to show up,
it is trying to use FP register because that is what the work around says to use
[17:19] <ngupta> so back to, could u try gcc-4.0
[17:20] <pinskia> I did and it worked
[17:20] <ngupta> I have started a build with this patch anyway
[17:20] <pinskia> you might need to revert the work around though
[17:20] <ngupta> oh ok, u mean patch for PR13674?
[17:21] <pinskia> the one which is on the 3.4 branch yes
[17:22] <ngupta> ok, got it
[17:22] <ngupta> thx, will update the bug after testing it
[17:24] <pinskia> 2004-03-10  Alan Modra  <amodra@bigpond.net.au>
[17:24] <pinskia>             Hartmut Penner  <hpenner@de.ibm.com>
[17:25] <ngupta> BTW, I will also CC dje/hpenner on this bug.
[17:25] <pinskia> one from http://gcc.gnu.org/ml/gcc-cvs/2004-03/msg00482.html
by the way

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hpenner at de dot ibm dot
                   |                            |com, dje at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2005-05-21  0:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  8:38 [Bug middle-end/21616] New: " raj dot khem at gmail dot com
2005-05-17  8:43 ` [Bug middle-end/21616] " raj dot khem at gmail dot com
2005-05-17  9:58 ` amodra at bigpond dot net dot au
2005-05-20 17:43 ` [Bug target/21616] " guptan at hotmail dot com
2005-05-21  0:14 ` [Bug target/21616] [3.4 only] " pinskia at gcc dot gnu dot org
2005-05-21  0:20 ` pinskia at gcc dot gnu dot org
2005-05-21  0:28 ` guptan at hotmail dot com [this message]
2005-05-24 20:43 ` guptan at hotmail dot com
     [not found] <bug-21616-10179@http.gcc.gnu.org/bugzilla/>
2005-10-07  4:03 ` gdr at gcc dot gnu dot org
2006-02-09 19:30 ` dje at gcc dot gnu dot org
2006-02-10 12:16 ` amodra at bigpond dot net dot au
2006-02-28 10:19 ` gdr at gcc dot gnu dot org
2006-02-28 15:27 ` dje at watson dot ibm dot com
2006-02-28 23:59 ` amodra at bigpond dot net dot au
2006-03-01  1:04 ` amodra at gcc dot gnu dot org
2006-03-01  1:06 ` amodra at bigpond dot net dot au

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=20050521002818.30991.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).