public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Eric Christopher <echristo@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
	Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	binutils@sources.redhat.com
Subject: Re: "Error: constant too large" on mips gas
Date: Wed, 13 Apr 2005 17:55:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61L.0504131853170.31027@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <1113330310.5119.6.camel@localhost.localdomain>

On Tue, 12 Apr 2005, Eric Christopher wrote:

> >  Well, no code example as I haven't touched it yet, but semantically-wise 
> > I think calls to expr() should should be able to specify the width of the 
> > ALU word to operate on and whether to treat literals as signed or not.  
> > Then any literal will get internally either zero- or sign-extended from 
> > the specified width to the width of the internal representation (i.e that 
> > of offsetT) as will any results produced.  Encountering a literal wider 
> > than the specified width should probably result in treating it as O_big.
> > 
> 
> This is close to what I was thinking of yesterday. One thought was that
> any literal that comes in as a "load address" should be considered to be
> sign extended to the size of the register, and a "load register" should
> be zero extended.

 Certainly, but that's something that callers have to take into account as 
expr() itself cannot make such a decision.

  Maciej

  reply	other threads:[~2005-04-13 17:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  3:35 Atsushi Nemoto
2005-04-04  8:58 ` Atsushi Nemoto
2005-04-04 13:37   ` Maciej W. Rozycki
2005-04-04 13:40     ` Daniel Jacobowitz
2005-04-04 14:00       ` Maciej W. Rozycki
2005-04-04 18:10     ` Eric Christopher
2005-04-05 18:41       ` Maciej W. Rozycki
2005-04-05 18:41         ` Eric Christopher
2005-04-05 18:56         ` Daniel Jacobowitz
2005-04-09 15:31         ` Daniel Jacobowitz
2005-04-09 17:47           ` Eric Christopher
2005-04-11 18:23             ` Maciej W. Rozycki
2005-04-11 21:40               ` Eric Christopher
2005-04-12 18:07                 ` Maciej W. Rozycki
2005-04-12 18:25                   ` Eric Christopher
2005-04-13 17:55                     ` Maciej W. Rozycki [this message]
2005-04-15  1:12               ` Atsushi Nemoto
2005-04-17 12:22                 ` Atsushi Nemoto
2005-04-18  6:25                 ` Atsushi Nemoto
2005-04-18  8:53                   ` Atsushi Nemoto
2005-04-05  2:38     ` Atsushi Nemoto
2005-04-05  4:28       ` Atsushi Nemoto
2005-04-05  4:34         ` Thiemo Seufer

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=Pine.LNX.4.61L.0504131853170.31027@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=binutils@sources.redhat.com \
    --cc=drow@false.org \
    --cc=echristo@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).