From: Richard Henderson <rth@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Target deprecation list
Date: Tue, 15 Apr 2003 21:00:00 -0000 [thread overview]
Message-ID: <20030415203323.GB12355@redhat.com> (raw)
In-Reply-To: <200304150722.h3F7MvMX015260@doubledemon.codesourcery.com>
On Tue, Apr 15, 2003 at 12:22:57AM -0700, Mark Mitchell wrote:
> I asked the folks that replied whether they
> were using recent versions of GCC on their target; if they weren't, I
> asked if they planned to do so.
Even this is not enough. Someone has to be willing to *maintain*
this code. Thus I think the requirements to keep
> arc-*-*
> i960-*-*
should be higher than for the others (which only keep os support
for an otherwise maintained cpu).
r~
next prev parent reply other threads:[~2003-04-15 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 10:24 Mark Mitchell
2003-04-15 16:38 ` Michael S. Zick
2003-04-15 21:00 ` Richard Henderson [this message]
2003-04-15 21:20 ` Mark Mitchell
2003-04-15 21:47 ` Eric Christopher
2003-04-15 21:43 ` Jeff Epler
2003-04-18 0:14 ` Mark Mitchell
2003-04-18 5:02 ` Jeff Epler
2003-04-18 7:43 ` Mark Mitchell
2003-04-17 8:16 ` Nitin Gupta
2003-04-17 14:01 ` Joel Sherrill
2003-04-23 11:55 Nitin Gupta
2003-04-23 16:09 ` Zack Weinberg
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=20030415203323.GB12355@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).