From: Andi Kleen <ak@suse.de>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Kevin Handy <kth@srv.net>, Andi Kleen <ak@suse.de>, gcc@gcc.gnu.org
Subject: Re: patch/proposal: obsolete configurations in 3.1
Date: Mon, 15 Apr 2002 01:21:00 -0000 [thread overview]
Message-ID: <20020415093138.A4975@wotan.suse.de> (raw)
In-Reply-To: <20020415062313.GC968@codesourcery.com>
On Sun, Apr 14, 2002 at 11:23:13PM -0700, Zack Weinberg wrote:
> On Sun, Apr 14, 2002 at 04:18:45PM -0600, Kevin Handy wrote:
> > Andi Kleen wrote:
> > >
> > >Here are some more proposals:
> > >
> > >pdp10-*
> > >
> > I wouldn't advise dropping the PDP10, since it is making a
> > resurgance due to the emulators that have become available. I
> > believe this target is actually fairly new.
>
> There isn't a PDP10 backend in the current official tree. I know
> people are working on one, though. Andi, did you mean pdp11?
Yes, pdp11, sorry. But as it seems there are people using it still
it is probably better to keep it.
-Andi
next prev parent reply other threads:[~2002-04-15 7:31 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020412194555.GD320@codesourcery.com.suse.lists.egcs-patches>
2002-04-14 15:18 ` Andi Kleen
2002-04-14 15:29 ` Kevin Handy
2002-04-14 23:24 ` Zack Weinberg
2002-04-15 1:21 ` Andi Kleen [this message]
2002-04-15 6:35 ` Paul Koning
2002-04-15 7:46 ` Mark Mitchell
2002-04-15 8:07 ` David S. Miller
2002-04-15 8:16 ` Mark Mitchell
2002-04-15 12:59 ` mike stump
2002-04-15 13:23 ` Mark Mitchell
2002-04-16 2:37 ` Hans-Peter Nilsson
2002-04-16 22:40 ` David O'Brien
2002-04-15 10:45 ` Daniel Egger
2002-04-15 12:21 ` Hans-Peter Nilsson
2002-04-15 11:56 ` Hans-Peter Nilsson
2002-04-15 16:49 ` Richard Henderson
2002-04-15 8:20 ` Lars Brinkhoff
2002-04-15 8:33 ` Alan Lehotsky
2002-04-15 10:06 ` Zack Weinberg
2002-04-15 10:42 ` Mark Mitchell
2002-04-15 12:47 ` Janis Johnson
2002-04-25 16:56 ` Jason Merrill
2002-04-15 18:50 ` Stan Shebs
2002-04-16 9:39 ` Zack Weinberg
2002-04-16 9:59 ` Kaveh R. Ghazi
2002-04-18 9:29 ` Kai Henningsen
2002-04-18 10:13 ` Paul Koning
2002-04-19 12:36 ` Hans-Peter Nilsson
2002-04-15 12:50 ` mike stump
2002-04-15 19:31 ` Phil Edwards
2002-04-15 19:46 ` DJ Delorie
2002-04-15 20:08 ` Phil Edwards
2002-04-15 23:06 ` DJ Delorie
2002-04-16 7:01 ` Paul Koning
2002-04-15 23:24 ` Neil Booth
2002-04-16 6:08 ` Phil Edwards
2002-04-17 18:13 ` Zack Weinberg
2002-04-17 19:10 ` DJ Delorie
2002-04-17 20:26 ` Phil Edwards
2002-04-19 12:46 ` Hans-Peter Nilsson
2002-04-15 0:31 ` Zack Weinberg
2002-04-15 17:43 ` Stan Shebs
2002-04-15 17:07 ` David O'Brien
2002-04-16 0:44 ` Douglas B. Rupp
2002-04-16 4:32 ` Joel Sherrill
2002-04-16 7:08 ` Paul Koning
2002-04-16 7:22 ` Joel Sherrill
2002-04-16 3:41 ` Richard Earnshaw
2002-04-16 6:30 ` Nick Burrett
2002-04-15 8:13 Robert Dewar
2002-04-15 9:28 Richard Kenner
2002-04-15 13:03 Robert Dewar
2002-04-16 8:46 Dana, Eric
2002-04-16 9:21 ` 'Zack Weinberg'
2002-04-16 9:39 ` Michael Matz
2002-04-16 12:57 Dana, Eric
2002-04-26 8:46 Dana, Eric
2002-04-26 9:18 ` Janis Johnson
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=20020415093138.A4975@wotan.suse.de \
--to=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=kth@srv.net \
--cc=zack@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).