From: Mark Mitchell <mark@codesourcery.com>
To: meissner@cygnus.com
Cc: shebs@apple.com, msokolov@ivan.Harhan.ORG,
binutils@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: m68k MacOS target support?
Date: Mon, 11 Sep 2000 21:33:00 -0000 [thread overview]
Message-ID: <20000911213332P.mitchell@codesourcery.com> (raw)
In-Reply-To: <20000911235644.44631@cse.cygnus.com>
>>>>> "Michael" == Michael Meissner <meissner@cygnus.com> writes:
Michael> You never know. There is after all, somebody porting GCC
Michael> to the Dec-10 architecture, something like 10-15 years
Michael> after DEC stopped making them (I don't recall when the
Michael> plug was pulled). I seem to recall discussion about the
Michael> VAX and GCC working on pristine BSD 4.3 in the last 2
Michael> months. Unfortunately, the AS400 effort seems to be
Michael> running into a wall.
For the record, I don't think that we (as mainline GCC developers)
should worry about these kinds of platforms, and I think Stan's
comments show a very mature mode of thinking towards 68K Macs. There
is a large burden in dragging around old ports, trying to make sure
Makefiles work there, and so forth. If someone else wants to keep GCC
working on a Dec-10, or a PDP-11, or an SV3 system, or whatever that's
just great -- but I don't think we should worry about those systems
when maintaining GCC.
My two cents,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2000-09-11 21:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-09 12:33 Michael Sokolov
2000-09-11 20:47 ` Stan Shebs
2000-09-11 20:56 ` Michael Meissner
2000-09-11 21:33 ` Mark Mitchell [this message]
2000-09-12 0:02 ` lars brinkhoff
2000-09-12 0:15 ` Mark Mitchell
2000-09-12 3:26 ` lars brinkhoff
2000-09-12 7:23 ` Mark Mitchell
2000-09-12 11:16 ` Joe Buck
2000-09-12 11:22 ` Bernd Schmidt
2000-09-12 20:11 ` Mark Mitchell
2000-09-12 13:59 ` Stan Shebs
2000-09-12 17:55 ` Richard Henderson
2000-09-12 19:12 ` Stan Shebs
2000-09-12 22:44 ` "Dead" Ports (was: m68k MacOS target support?) Gerald Pfeifer
2000-09-13 9:26 ` Jeffrey A Law
2000-09-13 9:33 ` Bernd Schmidt
2000-09-13 11:40 ` Stan Shebs
2000-09-13 9:57 ` Bruce Korb
2000-09-13 3:17 ` m68k MacOS target support? Joseph S. Myers
2000-09-12 11:48 ` Toon Moene
2000-09-12 7:32 ` Jeffrey A Law
2000-09-12 11:11 ` PDP10 support (was Re: m68k MacOS target support?) Joe Buck
2000-09-13 14:51 ` PDP10 support Gerald Pfeifer
2000-09-14 0:15 ` lars brinkhoff
2000-09-14 7:47 ` Nick Ing-Simmons
2000-09-12 0:03 ` m68k MacOS target support? lars brinkhoff
2000-09-12 9:52 ` David Huggins-Daines
2000-09-12 8:11 Richard Kenner
2000-09-12 17:57 Michael Sokolov
2000-09-12 18:12 ` Richard Henderson
2000-09-12 18:19 ` Geoff Keating
2000-09-12 19:05 ` Stan Shebs
2000-09-12 18:08 Michael Sokolov
2000-09-12 18:18 Michael Sokolov
2000-09-12 18:43 Michael Sokolov
2000-09-12 19:44 ` Stan Shebs
2000-09-13 8:40 ` Joe Buck
2000-09-13 8:49 Michael Sokolov
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=20000911213332P.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=meissner@cygnus.com \
--cc=msokolov@ivan.Harhan.ORG \
--cc=shebs@apple.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).