From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: cgd@broadcom.com
Cc: Paul Koning <pkoning@equallogic.com>,
ths@networkno.de, echristo@redhat.com, newlib@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: [patch] adjust libgloss addresses for 64-bit
Date: Mon, 18 Apr 2005 12:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61L.0504181350540.29567@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <yov5fyxrep1z.fsf@xl-sj1-04.sj.broadcom.com>
On Fri, 15 Apr 2005 cgd@broadcom.com wrote:
> > With, "li" vs "dli" the definition is rather obvious and unambiguous.
> > It's not with "la" vs "dla". With the (n)64 ABI what should the
> > following macros expand to:
> > [ ... ]
>
> Whatever SGI's assembler expands them into? 8-)
Well, but does it actually fit all the variations of -mabi=/-march= that
we implement? I have no access to that tool, so I can't tell...
> With warnings for where that differs from historic GNU binutils
> behaviour?
Well, I'd rather warn about dangerous constructs.
Finding out the difference to historic GNU binutils behaviour may be
tough as for the corner cases the sets will be different depending on the
version chosen. If you're careful enough with that choice, you may
actually end up with disjoint sets... Trivial cases, like "la $2, 0" are
likely to have always worked as expected. ;-)
Maciej
next prev parent reply other threads:[~2005-04-18 12:58 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
2005-04-16 10:26 ` Richard Sandiford
2005-04-15 20:57 ` cgd
2005-04-18 12:58 ` Maciej W. Rozycki [this message]
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=Pine.LNX.4.61L.0504181350540.29567@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 \
--cc=pkoning@equallogic.com \
--cc=ths@networkno.de \
/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).