[Fwd: Re: Target deprecation, round three]

[Fwd: Re: Target deprecation, round three]

[Mark Mitchell]

[-- Attachment #1: Type: text/plain, Size: 202 bytes --]

I'm having a little trouble using the snazzy new mail client I've got...

Thanks, Daniel, for pointing out that I'd not sent this to the list!

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

[-- Attachment #2: Forwarded message - Re: Target deprecation, round three --]
[-- Type: message/rfc822, Size: 3035 bytes --]

From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Mitchell <mark@codesourcery.com>
Subject: Re: Target deprecation, round three
Date: Mon, 24 Feb 2003 18:28:36 -0500
Message-ID: <20030224232836.GA30171@nevyn.them.org>

Mark, FYI, you replied only to me :)

On Mon, Feb 24, 2003 at 03:22:34PM -0800, Mark Mitchell wrote:
> > I'm concerned that we're keeping support for the i370 based on some
> > work David says Red Hat has done on the port, which is not in the tree. 
> > I seem to recall messages to the effect of "the i370 port in FSF GCC
> > does not work, but there's this code in Red Hat somewhere that does";
> > my apologies if I'm misinterpreting someone.
> 
> Only Red Hat and/or its customers can speak to the status of that.  I
> believe David indicated that Red Hat was going to contribute their work,
> and that someone else is interested in working on i370.  We've certainly
> kept platforms around with less potential than that; at least we still
> know of people running i370 hardware.
> 
> Is there a Red Hat person who can speak to whether or not this port is
> going to get merged and when?
> 
> Normally, the biggest advantages of getting rid of a port are:
> 
> (1) You can avoid touching it every time you change something.
> 
> (2) You can get rid of special features in generic code that exist 
>     only  for that port.
> 
> I think here Zack is interested in (2): getting rid of EBCDIC.  I'd like
> to do that too -- but it's hard to do if the machines using EBCDIC are
> still being used.  I'd like to get rid of COFF, too -- but we're going
> to have to wait a while for that, especially given Windows. :-)
> 
> That's why I'd like to understand more about how EBCDIC impacts
> multi-character support.
> 
> -- 
> Mark Mitchell
> CodeSourcery, LLC
> mark@codesourcery.com
> 
> 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer