From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23455 invoked by alias); 5 Jun 2009 15:49:00 -0000 Received: (qmail 23445 invoked by uid 22791); 5 Jun 2009 15:48:59 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 15:48:54 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id B191610F69; Fri, 5 Jun 2009 15:48:51 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id 8245410E5D; Fri, 5 Jun 2009 15:48:51 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1MCbez-0003JT-Mu; Fri, 05 Jun 2009 11:48:49 -0400 Date: Fri, 05 Jun 2009 15:49:00 -0000 From: Daniel Jacobowitz To: Paul Edwards Cc: Ulrich Weigand , gcc@gcc.gnu.org Subject: Re: i370 port Message-ID: <20090605154849.GA12676@caradoc.them.org> Mail-Followup-To: Paul Edwards , Ulrich Weigand , gcc@gcc.gnu.org References: <200906051520.n55FKg7T016481@d12av02.megacenter.de.ibm.com> <69CCB0B6B70141F0BCD2BAFA6DDF314F@Paullaptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <69CCB0B6B70141F0BCD2BAFA6DDF314F@Paullaptop> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-06/txt/msg00107.txt.bz2 On Sat, Jun 06, 2009 at 01:39:07AM +1000, Paul Edwards wrote: >> I understand current GCC supports various source and target character >> sets a lot better out of the box, so it may be EBCDIC isn't even an >> issue any more. > > It looks that way from what I've seen of 3.4.6 so far. However, I > won't know for sure until it's on the host and self-generating. Why are you migrating to 3.4.6 now, instead of to a current version? If you want to include this in mainline some day, then eventually it has to be caught up - and 3.4.6 is older than it may appear from the release date, since it branched off of mainline five years ago. A lot has changed since then. -- Daniel Jacobowitz CodeSourcery