From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32063 invoked by alias); 5 Jun 2009 15:57:28 -0000 Received: (qmail 32052 invoked by uid 22791); 5 Jun 2009 15:57:27 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rv-out-0708.google.com (HELO rv-out-0708.google.com) (209.85.198.244) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 15:57:21 +0000 Received: by rv-out-0708.google.com with SMTP id l33so190238rvb.56 for ; Fri, 05 Jun 2009 08:57:19 -0700 (PDT) Received: by 10.141.137.16 with SMTP id p16mr3238806rvn.200.1244217439569; Fri, 05 Jun 2009 08:57:19 -0700 (PDT) Received: from Paullaptop (124-168-137-88.dyn.iinet.net.au [124.168.137.88]) by mx.google.com with ESMTPS id f42sm285397rvb.51.2009.06.05.08.57.17 (version=SSLv3 cipher=RC4-MD5); Fri, 05 Jun 2009 08:57:19 -0700 (PDT) Message-ID: <654E603FCD3249F687040C94EB83D171@Paullaptop> From: "Paul Edwards" To: "Daniel Jacobowitz" Cc: "Ulrich Weigand" , References: <200906051520.n55FKg7T016481@d12av02.megacenter.de.ibm.com> <69CCB0B6B70141F0BCD2BAFA6DDF314F@Paullaptop> <20090605154849.GA12676@caradoc.them.org> In-Reply-To: <20090605154849.GA12676@caradoc.them.org> Subject: Re: i370 port Date: Fri, 05 Jun 2009 15:57:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit 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/msg00110.txt.bz2 >>> 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. 3.4.6 made some revamps to the i370 port (compared to 3.2.3), and I need to make sure those changes have been digested, and no code has been lost, so that I can pick up the final i370 port and move it. It's less daunting to get 3.4.6 working first. At least there the target actually exists and does obstensibly appear to work! Migrating from 3.4.6 to 4.x is not going to be made any bigger a deal. It's not like someone else is making incompatible changes to the i370 port at the same time as me! BFN. Paul.