From: "Maciej W. Rozycki" <macro@mips.com>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
Eric Christopher <echristo@redhat.com>,
binutils@sources.redhat.com,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] MIPS gas/ld test suite portability fixes
Date: Wed, 23 Feb 2005 19:22:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0502231519280.21383@perivale.mips.com> (raw)
In-Reply-To: <87650js49f.fsf@firetop.home>
On Wed, 23 Feb 2005, Richard Sandiford wrote:
> I don't buy that, but it's probably best not to go there ;)
I agree with you -- I think the "-mabi=" option is best left having no
influence on "-march=". OTOH, using mipsisa32-* tools for building n32 or
(n)64 binaries may make sense, especially when done occasionally only
which would not justify obtaining a full 64-bit setup. It may even
actually work for non-trivial builds as long as they are free-standing,
including, but probably not limited to the Linux kernel.
Maciej
next prev parent reply other threads:[~2005-02-23 15:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 19:24 Maciej W. Rozycki
2005-02-22 20:21 ` Daniel Jacobowitz
2005-02-22 21:15 ` Maciej W. Rozycki
2005-02-22 21:24 ` Daniel Jacobowitz
2005-02-22 23:38 ` Thiemo Seufer
2005-02-22 23:53 ` Maciej W. Rozycki
2005-02-23 0:05 ` Thiemo Seufer
2005-02-23 0:06 ` Eric Christopher
2005-02-23 0:57 ` Thiemo Seufer
2005-02-23 8:32 ` Eric Christopher
2005-02-23 8:34 ` Thiemo Seufer
2005-02-23 9:38 ` Eric Christopher
2005-02-23 9:47 ` Thiemo Seufer
2005-02-23 9:57 ` Thiemo Seufer
2005-02-23 14:26 ` Richard Sandiford
2005-02-23 16:39 ` Thiemo Seufer
2005-02-23 17:05 ` Richard Sandiford
2005-02-23 19:22 ` Maciej W. Rozycki [this message]
2005-02-24 1:47 ` Thiemo Seufer
2005-02-24 15:53 ` 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.61.0502231519280.21383@perivale.mips.com \
--to=macro@mips.com \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=macro@linux-mips.org \
--cc=rsandifo@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).