public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Paul Koning <pkoning@equallogic.com>
Cc: macro@linux-mips.org, echristo@redhat.com,
	newlib@sources.redhat.com, binutils@sources.redhat.com,
	cgd@broadcom.com
Subject: Re: [patch] adjust libgloss addresses for 64-bit
Date: Fri, 15 Apr 2005 19:35:00 -0000	[thread overview]
Message-ID: <20050415193522.GH21496@hattusa.textio> (raw)
In-Reply-To: <16992.5593.542000.552762@gargle.gargle.HOWL>

Paul Koning wrote:
> >>>>> "Maciej" == Maciej W Rozycki <macro@linux-mips.org> writes:
> 
>  Maciej> But in principle you are right for consistency the presence
>  Maciej> or the lack of the "d" prefix should imply the size of the
>  Maciej> operands used as it is so for other assembly instructions.
>  Maciej> So how about disabling the "wrong" macros completely?  That
>  Maciej> is using as_bad() for these two "dla/la used to load..."
>  Maciej> messages just below "do_la" that are currently warnings.
>  Maciej> After all these load address macros are the only place where
>  Maciej> non-default address calculation rules can be argued about at
>  Maciej> all -- the interpretation of e.g.:
> 
>  Maciej> lh $2, 0x80000000 lh $2, 0x80000000($3) lh $2, foo +
>  Maciej> 0x80000000($3) lh $2, foo + 0xc000000080000000($3)
> 
> One answer would be to use an implicit DLA for N64, and LA otherwise.
> I was thinking more about explicitly written LA vs. DLA.
> 
> All this demonstrates once again that the whole built-in macro stuff
> in the MIPS assembler was a design blunder from day one.  Sigh.
> 
> Fortunately, GCC no longer uses any of this...

For 64bit non-PIC it still does.


Thiemo

  reply	other threads:[~2005-04-15 19:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 22:08 Eric Christopher
2005-04-14 22:38 ` Thiemo Seufer
2005-04-15 10:32   ` Maciej W. Rozycki
2005-04-15 11:28     ` Thiemo Seufer
2005-04-15 16:50       ` Eric Christopher
2005-04-15 19:37         ` Thiemo Seufer
2005-04-15 16:50     ` Eric Christopher
2005-04-15 17:03       ` Maciej W. Rozycki
2005-04-15 17:07         ` Eric Christopher
2005-04-18 12:46           ` Maciej W. Rozycki
2005-04-15 17:18         ` Thiemo Seufer
2005-04-15 17:35           ` Paul Koning
2005-04-15 18:56             ` Maciej W. Rozycki
2005-04-15 19:25               ` Paul Koning
2005-04-15 19:28               ` Paul Koning
2005-04-15 19:35                 ` Thiemo Seufer [this message]
2005-04-16 10:26                   ` Richard Sandiford
2005-04-15 20:57               ` cgd
2005-04-18 12:58                 ` Maciej W. Rozycki
2005-04-18 19:32                   ` Eric Christopher
2005-04-16 10:31               ` Richard Sandiford

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=20050415193522.GH21496@hattusa.textio \
    --to=ths@networkno.de \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=echristo@redhat.com \
    --cc=macro@linux-mips.org \
    --cc=newlib@sources.redhat.com \
    --cc=pkoning@equallogic.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).