From: Richard Sandiford <rdsandiford@googlemail.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: "Mark Mitchell" <mark@codesourcery.com>,
"Richard Guenther" <richard.guenther@gmail.com>,
<dclarke@blastwave.org>,
"Rainer Orth" <ro@techfak.uni-bielefeld.de>,
"Eric Botcazou" <ebotcazou@adacore.com>, <gcc@gcc.gnu.org>,
"David Edelsohn" <dje.gcc@gmail.com>
Subject: Re: Updating Primary and Secondary platform list for gcc-4.5 ???
Date: Tue, 24 Nov 2009 19:19:00 -0000 [thread overview]
Message-ID: <87y6lvwx0u.fsf@firetop.home> (raw)
In-Reply-To: <1B0EDB7E77DD48198510BAD9B902A291@glap> (Kaveh R. Ghazi's message of "Thu\, 12 Nov 2009 08\:00\:30 -0700")
"Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> writes:
> Agreed. I guess my remaining questions are for AIX and mipsisa64-elf.
>
> Can someone please confirm that mipsisa64-elf is a cross-compile-only target
> and therefore not relevant for host-based MPC portability testing?
Yes, that's right.
I'm sure it's technically possible to compile GCC with a mipsisa64-elf
compiler, but it would be hard, and it isn't a well-defined operation.
I don't think you could do it with the usual libgloss runtime environment;
you'd need to use a "real" OS.
Richard
next prev parent reply other threads:[~2009-11-24 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 16:50 Dennis Clarke
2009-11-09 16:59 ` Richard Guenther
2009-11-10 17:03 ` Mark Mitchell
2009-11-12 15:00 ` Kaveh R. Ghazi
2009-11-12 15:11 ` David Edelsohn
2009-11-12 15:43 ` Kaveh R. Ghazi
2009-11-24 19:19 ` Richard Sandiford [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-09 15:46 Dennis Clarke
2009-11-09 16:17 ` Rainer Orth
2009-11-07 16:56 Kaveh R. GHAZI
2009-11-07 17:39 ` Eric Botcazou
2009-11-09 15:34 ` Rainer Orth
2009-11-07 20:02 ` Gerald Pfeifer
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=87y6lvwx0u.fsf@firetop.home \
--to=rdsandiford@googlemail.com \
--cc=dclarke@blastwave.org \
--cc=dje.gcc@gmail.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=mark@codesourcery.com \
--cc=richard.guenther@gmail.com \
--cc=ro@techfak.uni-bielefeld.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).