public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.icarus.com>
To: egcs@cygnus.com
Subject: cross from alpha to arm
Date: Wed, 15 Oct 1997 09:15:00 -0000	[thread overview]
Message-ID: <199710151615.JAA06582@icarus.icarus.com> (raw)

This very simple patch allows egcs to successfully build libgcc for the
arm from a Linux/alpha host. I can't say if it fixes the root of the problem,
but it certainly gets me over the immediate hurdle. This seems to be the
only place left where 64bit host --> 32bit arm is confused.

*** egcs-971008/gcc/config/arm/arm.c	Mon Aug 11 08:57:24 1997
--- ../egcs-971008/gcc/config/arm/arm.c	Tue Oct 14 18:31:16 1997
***************
*** 407,412 ****
--- 407,416 ----
  {
    unsigned HOST_WIDE_INT mask = ~0xFF;
  
+ #if HOST_BITS_PER_WIDE_INT > 32
+   if (i & 0xffffffff00000000LL) return FALSE;
+ #endif
+ 
    /* Fast return for 0 and powers of 2 */
    if ((i & (i - 1)) == 0)
      return TRUE;



             reply	other threads:[~1997-10-15  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-15  9:15 Stephen Williams [this message]
1997-10-15 11:04 ` Richard Henderson
1997-10-15 14:33   ` Stephen Williams
1997-10-15 20:16   ` Richard Earnshaw

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=199710151615.JAA06582@icarus.icarus.com \
    --to=steve@icarus.icarus.com \
    --cc=egcs@cygnus.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 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).