From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Eric Christopher <echristo@redhat.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, binutils@sources.redhat.com
Subject: Re: "Error: constant too large" on mips gas
Date: Tue, 05 Apr 2005 18:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61L.0504051922001.9632@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <1112638226.5320.0.camel@localhost.localdomain>
On Mon, 4 Apr 2005, Eric Christopher wrote:
> > gas/:
> > 2005-04-04 Maciej W. Rozycki <macro@linux-mips.org>
> >
> > * config/tc-mips.c (IS_ZEXT_32BIT_NUM): New macro.
> > (normalize_address_expr): New function to sign-extend address
> > offsets that fit into 32 bits in 32-bit mode.
> > (macro_build_ldst_constoffset): Use normalize_address_expr()
> > instead of a handcoded sequence.
> > (load_register): Likewise. Report oversized numbers in a useful
> > way.
> > (macro) [ld_st, ldd_std]: Reject all oversized offsets, not only
> > for constant addresses. Report oversized numbers in a useful way.
> > (mips_ip): Use normalize_address_expr() for addresses.
> >
> > gas/testsuite/:
> > 2005-04-04 Maciej W. Rozycki <macro@linux-mips.org>
> >
> > * gas/mips/ldstla-32.s: Exclude offsets that are now meant to fail
> > and include more instructions/offsets that are meant to succeed.
> > Use $4 instead $3 to avoid register dependencies.
> > * gas/mips/ldstla-32.d: Update accordingly.
> > * gas/mips/ldstla-32-shared.d: Likewise.
> > * gas/mips/ldstla-32-1.s: New test for offsets that are meant to
> > fail.
> > * gas/mips/ldstla-32-1.l: Stderr output for the new test.
> > * gas/mips/mips.exp: Run the new test (twice).
> >
> > OK to apply?
>
> OK. Some documentation on this probably wouldn't be amiss either :)
Well, given new error cases, I'll yet have a look at resolving them.
But specifically, what do you mean by "some documentation?" I mean these
error messages are self-documenting -- what else you'd consider useful?
Maciej
next prev parent reply other threads:[~2005-04-05 18:41 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 [this message]
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
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.0504051922001.9632@blysk.ds.pg.gda.pl \
--to=macro@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=binutils@sources.redhat.com \
--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).