From: cgd@broadcom.com
To: macro@ds2.pg.gda.pl
Cc: "Eric Christopher" <echristo@redhat.com>,
"Alexandre Oliva" <aoliva@redhat.com>,
"Thiemo Seufer" <ica2_ts@csv.ica.uni-stuttgart.de>,
binutils@sources.redhat.com
Subject: Re: check mips abi x linker emulation compatibility
Date: Tue, 20 May 2003 22:06:00 -0000 [thread overview]
Message-ID: <yov565o5mfy5.fsf@broadcom.com> (raw)
In-Reply-To: macro@ds2.pg.gda.pl's message of "Tue, 20 May 2003 21:07:50 +0000 (UTC)"
At Tue, 20 May 2003 21:07:50 +0000 (UTC), "Maciej W. Rozycki" wrote:
> As I understand, you don't like the names of configurations to be
> "mipsn32" and "mips64" for n32 and (n)64, respectively. What names do you
> propose, then? These two seem the least confusing for me.
Uh, "and mips64 means mips3 isn't confusing"? 8-)
So, at least the way things are going now, it looks like
"mips64-linux" tools (both binutils and gcc) will/should support all
three ABIs, with the default being n32.
I don't know that there's any reason to support an abi=64 default set
of tools, since really, people shouldn't be using abi=64 except with
certain extreme cases IMO. (more space for no gain.)
You need to do a little bit of work to get the glibc's all built, but
from what Alex has indicated to me the glibc folks aren't gonna bite
on configure CPU names w/ ABIs in them, so you have to do that anyway.
cgd
next prev parent reply other threads:[~2003-05-20 22:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 7:41 Alexandre Oliva
2003-03-24 7:58 ` Thiemo Seufer
2003-03-28 18:51 ` Alexandre Oliva
2003-05-04 21:25 ` Alexandre Oliva
2003-05-04 21:33 ` Thiemo Seufer
2003-05-05 5:55 ` Eric Christopher
2003-05-07 4:12 ` Alexandre Oliva
2003-05-07 4:34 ` Eric Christopher
[not found] ` <mailpost.1052280762.26483@news-sj1-1>
2003-05-07 5:03 ` cgd
2003-05-07 5:07 ` Alexandre Oliva
[not found] ` <mailpost.1052284059.27953@news-sj1-1>
2003-05-07 5:09 ` cgd
2003-05-07 5:17 ` Alexandre Oliva
2003-05-07 5:28 ` Eric Christopher
2003-05-07 5:51 ` Alexandre Oliva
2003-05-07 5:59 ` Eric Christopher
2003-05-07 5:09 ` Eric Christopher
2003-05-07 5:27 ` Alexandre Oliva
2003-05-07 6:39 ` Richard Sandiford
2003-05-07 15:38 ` Alexandre Oliva
2003-05-07 15:57 ` Richard Sandiford
2003-05-07 16:43 ` Eric Christopher
2003-05-07 17:04 ` Richard Sandiford
2003-05-07 17:07 ` Eric Christopher
2003-05-08 16:57 ` Alexandre Oliva
[not found] ` <mailpost.1052413109.28553@news-sj1-1>
2003-05-08 17:54 ` cgd
2003-05-08 18:19 ` Alexandre Oliva
2003-05-08 18:30 ` cgd
2003-05-08 22:22 ` Eric Christopher
2003-05-08 18:43 ` Thiemo Seufer
2003-05-15 0:22 ` Alexandre Oliva
2003-05-15 0:39 ` Eric Christopher
2003-05-15 1:59 ` Alexandre Oliva
2003-05-15 2:14 ` Eric Christopher
[not found] ` <mailpost.1052327094.17221@news-sj1-1>
2003-05-08 0:36 ` cgd
2003-05-07 16:17 ` Thiemo Seufer
2003-05-20 20:40 ` Maciej W. Rozycki
2003-05-20 20:55 ` Thiemo Seufer
2003-05-20 21:00 ` Eric Christopher
2003-05-20 21:07 ` Maciej W. Rozycki
2003-05-20 21:19 ` Eric Christopher
2003-05-20 22:42 ` Alexandre Oliva
2003-05-20 22:49 ` Eric Christopher
2003-05-21 10:48 ` Maciej W. Rozycki
[not found] ` <mailpost.1053464869.12015@news-sj1-1>
2003-05-20 22:06 ` cgd [this message]
2003-05-21 11:06 ` Maciej W. Rozycki
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=yov565o5mfy5.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=macro@ds2.pg.gda.pl \
/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).