From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27814 invoked by alias); 24 Nov 2009 14:36:39 -0000 Received: (qmail 27805 invoked by uid 22791); 24 Nov 2009 14:36:38 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-px0-f176.google.com (HELO mail-px0-f176.google.com) (209.85.216.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 24 Nov 2009 14:36:34 +0000 Received: by pxi6 with SMTP id 6so3318900pxi.0 for ; Tue, 24 Nov 2009 06:36:33 -0800 (PST) Received: by 10.114.4.25 with SMTP id 25mr12420649wad.164.1259073392117; Tue, 24 Nov 2009 06:36:32 -0800 (PST) Received: from Paullaptop (203-158-49-56.dyn.iinet.net.au [203.158.49.56]) by mx.google.com with ESMTPS id 21sm3464835pxi.8.2009.11.24.06.36.28 (version=SSLv3 cipher=RC4-MD5); Tue, 24 Nov 2009 06:36:30 -0800 (PST) Message-ID: <16E3FD79CD4C486BAFBEF0D846C7A1C9@Paullaptop> From: "Paul Edwards" To: "Ulrich Weigand" Cc: "Ralf Wildenhues" , "Ian Lance Taylor" , References: <200911241405.nAOE5Jsd022678@d12av02.megacenter.de.ibm.com> In-Reply-To: <200911241405.nAOE5Jsd022678@d12av02.megacenter.de.ibm.com> Subject: Re: i370 port - 3.4.6 to 4.4 upgrade attempt Date: Tue, 24 Nov 2009 14:36: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-11/txt/msg00635.txt.bz2 > I can see one significant change: the GCC middle-end now no > longer supports base-16 floating point at all. The old i370 > port was the only user of this feature, and some time after > the port was removed, the middle-end support was removed as > well in order to simplify floating-point handling code. Hmmm. Well I don't know anything about floating point. Thanks very much for all your comments. I will see what difference that makes. > Note that I'd expect that with the above obvious issues fixed, > you may well run into additional problems in moving the port > forward ... At some point, it will be necessary to be able > to debug the back-end and resolve problems. Ok, well what I did in the original (3.2) port was to ANSIfy it and then use different debuggers (Borland, Watcom) on my Windows box. I'll see what I can come up with this time. > Overall, I still think that adding HLASM support to the s390 > back-end would probably be a simpler task ... Well in that case, maybe now is the time to be doing exactly that. I could make 3.4.6 the last of the i370 ports. Can you tell me what is required to convert s390, which has a very alien assembler output, into hlasm? And that brings me to another question. The i370 hlasm port uses tabs in every instruction to separate the instruction and operand. This is not valid in hlasm. In order to get around this, I ended up doing a #define for putc etc to channel everything through my own routine which converted those tabs into an appropriate number of spaces. I suspect there's a neater way to do things, but I never stumbled across that in my travels. Thanks. Paul.