All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Kjeld Borch Egevang <kjelde@mips.com>
Cc: linux-mips mailing list <linux-mips@oss.sgi.com>
Subject: Re: gcc crash
Date: Sat, 29 Sep 2001 01:35:49 -0700	[thread overview]
Message-ID: <20010929013549.A4044@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0109271657250.1742-100000@coplin19.mips.com>; from kjelde@mips.com on Thu, Sep 27, 2001 at 04:59:47PM +0200

On Thu, Sep 27, 2001 at 04:59:47PM +0200, Kjeld Borch Egevang wrote:
> When I compile the following function with "gcc -O2" the compiler crashes.
> Is this a known problem?
> 
> static float sp_f2l(float x)
> {
>     long l, *xl;
>     float y;
> 
>     xl = (void *)&y;
>     l = x;
>     *xl = l;
>     return y;
> }
> 
> I use gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-97.2)
> 

I back ported this from gcc in CVS to gcc 2.96. It works for me. It
will be in the next RedHat 7.1/mips update.


H.J.
-----
2001-09-29  H.J. Lu <hjl@gnu.org>

	* gcc/emit-rtl.c (subreg_hard_regno): Comment out dubious code.

--- gcc/emit-rtl.c.subreg	Sat Sep 29 01:21:24 2001
+++ gcc/emit-rtl.c	Sat Sep 29 01:22:06 2001
@@ -734,6 +734,7 @@ subreg_hard_regno (x, check_mode)
 
   final_regno = SUBREG_REGNO (x);
 
+#if 0
   /* Punt if what we end up with is not a valid regno in
      the SUBREG's mode, or we went past the end of the inner
      REG's mode, or we overflow past the last hard regno.  */
@@ -743,6 +744,7 @@ subreg_hard_regno (x, check_mode)
 	   HARD_REGNO_NREGS (base_regno, GET_MODE (reg)))
        || final_regno >= FIRST_PSEUDO_REGISTER)
     abort ();
+#endif
 
   return final_regno;
 }

      parent reply	other threads:[~2001-09-29  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-27 14:59 gcc crash Kjeld Borch Egevang
2001-09-28 12:37 ` Keith Owens
2001-09-28 17:05   ` Ralf Baechle
2001-09-29  8:35 ` H . J . Lu [this message]

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=20010929013549.A4044@lucon.org \
    --to=hjl@lucon.org \
    --cc=kjelde@mips.com \
    --cc=linux-mips@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.