From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29776 invoked by alias); 5 Jun 2009 15:24:00 -0000 Received: (qmail 29768 invoked by uid 22791); 5 Jun 2009 15:23:59 -0000 X-SWARE-Spam-Status: No, hits=-2.2 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.251) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 15:23:51 +0000 Received: by rv-out-0708.google.com with SMTP id l33so178294rvb.56 for ; Fri, 05 Jun 2009 08:23:49 -0700 (PDT) Received: by 10.141.29.14 with SMTP id g14mr3340141rvj.232.1244215429582; Fri, 05 Jun 2009 08:23:49 -0700 (PDT) Received: from Paullaptop (124-168-137-88.dyn.iinet.net.au [124.168.137.88]) by mx.google.com with ESMTPS id b39sm3967298rvf.3.2009.06.05.08.23.47 (version=SSLv3 cipher=RC4-MD5); Fri, 05 Jun 2009 08:23:49 -0700 (PDT) Message-ID: <3E973779D9924C328F8BAD8A1168BA7B@Paullaptop> From: "Paul Edwards" To: "Joseph S. Myers" Cc: References: <22637DCC73B54BD1B74D5A5F1939C6AF@Paullaptop> In-Reply-To: Subject: Re: i370 port Date: Fri, 05 Jun 2009 15:24: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/msg00101.txt.bz2 >> The port is to a pure C90 environment (ie not posix, not unix). It was a >> major effort to achieve that, and it has only just been completed to the >> point where the compiler recompiles itself with full optimization. The >> environment where it runs is not set up to run shell scripts or makes >> or test suites. It's set up to run JCL, and there's a stack of JCL card >> decks to allow GCC to compile, which would be good to have included >> in the i370 directory. > > You can test a cross compiler if you have some way of copying a test > executable to the i370 system It doesn't build executables either. Only the "-S" option is used. With that restriction, GCC merely reads a bunch of text files and writes a text file, and thus is amenable to being a pure C90 application. That's how it manages to work at all. > running it and getting its output and exit > status back (actually you don't need to be able to get the exit status > since DejaGnu has wrappers to include it in the output if needed). It so happens that MVS/380 has the ability to be run in batch, and extracting the exit code won't be a problem either. Note however that I normally do all my GCC work in Windows, and the batch running etc is done with batch files. > There > is no need for the target to be able to run shell scripts or makes. You > would need to write your own DejaGnu board file that deals with copying > to/from the i370 system and running programs there. The testsuite > routinely runs for much more limited embedded systems (using appropriate > board files). I have a large backlog of work to do with the i370 port already, starting with getting gcc 3.4.6 running natively. Isn't that a more productive thing to do? Even after 3.4.6 is done, so that every scrap of code is available, then there's version 4 to do! BFN. Paul.