From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11881 invoked by alias); 5 Jun 2009 20:45:29 -0000 Received: (qmail 11865 invoked by uid 22791); 5 Jun 2009 20:45:26 -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.249) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 20:45:20 +0000 Received: by rv-out-0708.google.com with SMTP id l33so274987rvb.56 for ; Fri, 05 Jun 2009 13:45:18 -0700 (PDT) Received: by 10.141.48.10 with SMTP id a10mr3303035rvk.250.1244234718291; Fri, 05 Jun 2009 13:45:18 -0700 (PDT) Received: from Paullaptop (124-168-137-88.dyn.iinet.net.au [124.168.137.88]) by mx.google.com with ESMTPS id f21sm531492rvb.5.2009.06.05.13.45.15 (version=SSLv3 cipher=RC4-MD5); Fri, 05 Jun 2009 13:45:17 -0700 (PDT) Message-ID: From: "Paul Edwards" To: "Joseph S. Myers" Cc: "Daniel Jacobowitz" , "Ulrich Weigand" , References: <200906051520.n55FKg7T016481@d12av02.megacenter.de.ibm.com> <69CCB0B6B70141F0BCD2BAFA6DDF314F@Paullaptop> <20090605154849.GA12676@caradoc.them.org> <654E603FCD3249F687040C94EB83D171@Paullaptop> In-Reply-To: Subject: Re: i370 port Date: Fri, 05 Jun 2009 20:45: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/msg00116.txt.bz2 >> 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. > > But there were probably also (mechanical) changes to the port between when > 3.4 branched (long before 3.4.6 was released) and when the port was > removed from trunk - that's why the last revision before it was removed > from trunk may be a better starting point. Ok, I understand now. So there were some changes, that would nominally have made it to GCC 4, but were in fact never officially released, because it was dropped before release. So, prior to starting a GCC 4 port (ie the changes may not be desirable for the GCC 3.4.6 port I am currently working on), I need to get GCC 3.4 as a base, GCC 3.4.6 as one derivative, and SVN 77215, then do a 3-way diff/merge to obtain the "nominal GCC 4" changes. Or perhaps not. I don't want the 3.4.6 changes at that point, since anything of value will be covered by SVN 77215. So I need to use GCC 3.4.6 as the base, my personal version as one derivative, SVN 77215 as the second derivative, and feed that into the 3-way diff. Ok, I'll do that when I'm in a position to do the GCC 4 port attempt. I'm still months away from completing the GCC 3.4.6 port, and there are other MVS-related projects that are more important than what is basically a transparent 3.2.3 to 4 upgrade that will only start being useful when it enables something else to happen (such as the PL/1 front-end). So I'll be working on that stable 3.4.6 before taking my chances with what is basically an axed beta (SVN 77215), with still no indication of whether even a perfectly working self-compiling i370 target will be accepted unless the testsuite is working first (and even if it was working, that still may not be enough - as the next hoop may be an s390 merge - and a requirement to switch from 370 to 390). BFN. Paul.