public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/10315: [3.2/3.3 regression] [powerpc] ICE: in	extract_insn, at recog.c:2175
Date: Wed, 23 Apr 2003 18:26:00 -0000	[thread overview]
Message-ID: <20030423182600.31468.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/10315; it has been noted by GNATS.

From: Geoff Keating <geoffk@geoffk.org>
To: dje@watson.ibm.com
Cc: s.bosscher@student.tudelft.nl, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
   adconrad@0c3.net, 186299@bugs.debian.org
Subject: Re: optimization/10315: [3.2/3.3 regression] [powerpc] ICE: in	extract_insn, at recog.c:2175
Date: Wed, 23 Apr 2003 11:14:26 -0700

 > Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>, gcc-gnats@gcc.gnu.org,
 >    gcc-bugs@gcc.gnu.org, adconrad@0c3.net, 186299@bugs.debian.org
 > Date: Tue, 22 Apr 2003 23:14:37 -0400
 > From: David Edelsohn <dje@watson.ibm.com>
 > X-OriginalArrivalTime: 23 Apr 2003 03:14:43.0793 (UTC) FILETIME=[7C849410:01C30946]
 > 
 > 	The problem is easy_fp_constant():
 > 
 >   /* If we are using V.4 style PIC, consider all constants to be hard.  */
 >   if (flag_pic && DEFAULT_ABI == ABI_V4)
 >     return 0;
 > 
 > This means that "input_operand" predicate fails for movdf_hardfloat32 when
 > presented with const_double:DF.  I'm not sure what's suppose to save us at
 > that point.
 
 In that case, the RTL should never have been generated...
 
 -- 
 - Geoffrey Keating <geoffk@geoffk.org>


             reply	other threads:[~2003-04-23 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23 18:26 Geoff Keating [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 14:06 David Edelsohn
2003-04-24  4:56 Richard Henderson
2003-04-23 22:56 Richard Henderson
2003-04-23 20:16 David Edelsohn
2003-04-23  3:16 David Edelsohn
2003-04-07  7:16 Steven Bosscher
2003-04-05 13:56 Matthias Klose

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=20030423182600.31468.qmail@sources.redhat.com \
    --to=geoffk@geoffk.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).