public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Clifton <nickc@redhat.com>
Cc: Julian Brown <julian@codesourcery.com>, binutils@sources.redhat.com
Subject: Re: [PATCH, ARM] Fix out-of-range immediate assembly errors on 64-bit   hosts
Date: Thu, 15 Jun 2006 14:58:00 -0000	[thread overview]
Message-ID: <20060615145609.GA20396@nevyn.them.org> (raw)
In-Reply-To: <449115D9.4020809@redhat.com>

On Thu, Jun 15, 2006 at 09:10:01AM +0100, Nick Clifton wrote:
> Or just have the comment in the code.  (Hmm, do we need to worry about 
> compiling on 16-bit hosts where ">> 16" would trigger a warning ?)

No, we do not.  It's standard for GNU tools to only support 32-bit
hosts, even when they support 16-bit targets.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-06-15 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 17:56 Julian Brown
2006-06-12 11:45 ` Nick Clifton
2006-06-12 13:50   ` Julian Brown
2006-06-15  9:54     ` Nick Clifton
2006-06-15 14:58       ` Daniel Jacobowitz [this message]
2006-09-06 13:27       ` Julian Brown
2006-11-14 12:42         ` Nick Clifton

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=20060615145609.GA20396@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sources.redhat.com \
    --cc=julian@codesourcery.com \
    --cc=nickc@redhat.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).