From: "H . J . Lu" <hjl@lucon.org>
To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Cc: binutils@sourceware.cygnus.com
Subject: Re: [PATCH] Code cleanup in tc-mips.c
Date: Wed, 22 Aug 2001 08:36:00 -0000 [thread overview]
Message-ID: <20010822083601.A24798@lucon.org> (raw)
In-Reply-To: <20010822023927.P30301@rembrandt.csv.ica.uni-stuttgart.de>
On Wed, Aug 22, 2001 at 02:39:27AM +0200, Thiemo Seufer wrote:
> H . J . Lu wrote:
> [snip]
> > > > It is documented. I think it may have better
> > > > support in gcc than other 64bit misp ABI.
> > >
> > > Old ECOFF isn't even an issue. Did you mean something else?
> >
> > The SGI 64bit ABI corrected a few mistakes in the 32bit SVR4 MIPS ABI.
> > But it also has other stuff we may not need. I have a wish list for
> > a 64bit MIPS ABI.
>
> What do you think is superfluous? QuickStart?
Yes. We don't need it and anything related to it. Jakub is working on
prelink for glibc. But the MIPS ABI doesn't help.
>
> [snip]
> > BTW, all my emails sent to you are blocked. I have to send it to
> > the binutils mailing list.
>
> Our DNS can't resolve the MX for lucon.org. Local problem here,
> I assume. :-(
Let me give it a try this time.
H.J.
prev parent reply other threads:[~2001-08-22 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 12:15 Thiemo Seufer
2001-08-21 12:50 ` Eric Christopher
2001-08-21 13:14 ` Thiemo Seufer
2001-08-21 15:12 ` Eric Christopher
2001-08-21 15:27 ` Thiemo Seufer
2001-08-21 15:30 ` Eric Christopher
2001-08-24 10:46 ` Thiemo Seufer
2001-08-24 11:49 ` Eric Christopher
2001-08-21 15:36 ` H . J . Lu
[not found] ` <20010822012500.O30301@rembrandt.csv.ica.uni-stuttgart.de>
2001-08-21 16:58 ` H . J . Lu
2001-08-21 17:39 ` Thiemo Seufer
2001-08-22 8:36 ` H . J . Lu [this message]
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=20010822083601.A24798@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.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).