From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17363 invoked by alias); 5 Jun 2009 15:44:05 -0000 Received: (qmail 17349 invoked by uid 22791); 5 Jun 2009 15:44:04 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_FAIL X-Spam-Check-By: sourceware.org Received: from mx20.gnu.org (HELO mx20.gnu.org) (199.232.41.8) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 05 Jun 2009 15:43:57 +0000 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MCbaF-0002iB-Ht for gcc@gcc.gnu.org; Fri, 05 Jun 2009 11:43:55 -0400 Received: (qmail 13031 invoked from network); 5 Jun 2009 15:43:54 -0000 Received: from unknown (HELO digraph.polyomino.org.uk) (joseph@127.0.0.2) by mail.codesourcery.com with ESMTPA; 5 Jun 2009 15:43:54 -0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.69) (envelope-from ) id 1MCbaD-0002yv-IJ; Fri, 05 Jun 2009 15:43:53 +0000 Date: Fri, 05 Jun 2009 15:44:00 -0000 From: "Joseph S. Myers" To: Ulrich Weigand cc: Paul Edwards , gcc@gcc.gnu.org Subject: Re: i370 port In-Reply-To: <200906051520.n55FKg7T016481@d12av02.megacenter.de.ibm.com> Message-ID: References: <200906051520.n55FKg7T016481@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Detected-Operating-System: by mx20.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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/msg00105.txt.bz2 On Fri, 5 Jun 2009, Ulrich Weigand 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. If there are other problems related to MVS host I think the EBCDIC support is largely theoretical and not tested on any actual EBCDIC host (or target). cpplib knows the character set name UTF-EBCDIC, but whenever it does anything internally that involves the encoding of its internal character set it uses UTF-8 rules (which is not something valid to do with UTF-EBCDIC). -- Joseph S. Myers joseph@codesourcery.com