public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: cgd@broadcom.com
Cc: echristo@redhat.com, newlib@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: [patch] modify crt0.S for 64-bit address targets
Date: Wed, 06 Apr 2005 11:05:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61L.0504061152001.14106@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <yov53bu4767a.fsf@xl-sj1-02.sj.broadcom.com>

On Wed, 5 Apr 2005 cgd@broadcom.com wrote:

> I'm probably confused/mistaken but... i thought 'la' was supposed to
> generate a 32-bit address (and dla generate a 64-bit address)?  Or
> maybe they always generate the address of the ABI in use?  I
> forget... so much change.

 AFAIK, the only reason for both "dla" and "la" to exist is history and 
compatibility with existing code -- there is no need to encode the address 
size in the mnemonic as its already implied by the ABI in use.  
Therefore, as far as gas is concerned, both expand to the same code -- 
it's just they generate different warning messages and for different 
conditions: "dla" complains about being used for ABIs that have 32-bit 
registers and "la" does that for ones that have 64-bit addresses.

  Maciej

  reply	other threads:[~2005-04-06 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1112768205.5493.2.camel@localhost.localdomain>
     [not found] ` <mailpost.1112768909.17118@news-sj1-1>
2005-04-06  6:49   ` cgd
2005-04-06 11:05     ` Maciej W. Rozycki [this message]
2005-04-06 11:22       ` Thiemo Seufer
2005-04-06 14:40         ` Maciej W. Rozycki
2005-04-06 18:37     ` Eric Christopher
2005-04-06 19:31       ` Paul Koning
2005-04-06 19:35         ` Ian Lance Taylor
2005-04-06 21:35         ` Eric Christopher
2005-04-06 18:51 cgd
2005-04-06 19:01 ` Eric Christopher

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.0504061152001.14106@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=echristo@redhat.com \
    --cc=newlib@sources.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).