From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29766 invoked by alias); 4 Dec 2004 03:44:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 29749 invoked by uid 48); 4 Dec 2004 03:44:12 -0000 Date: Sat, 04 Dec 2004 03:44:00 -0000 Message-ID: <20041204034412.29748.qmail@sourceware.org> From: "roger at eyesopen dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041202142212.18785.darcypj@us.ibm.com> References: <20041202142212.18785.darcypj@us.ibm.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug middle-end/18785] [4.0 Regression] isdigit builtin function fails with EBCDIC character sets X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg00581.txt.bz2 List-Id: ------- Additional Comments From roger at eyesopen dot com 2004-12-04 03:44 ------- Hi P.J., Thanks for removing the i686 version of the attachment. But it looks like the 390x-ibm-tpf version of digit.i (attachment #1), also reveals that the isdigit call is being expanded as a macro in native . Can you confirm that there's actually a problem with the GCC builtin, for example, by showing that adding the command line option -fno-builtin-isdigit resolves the failure? If specifying -fno-builtin-isdigit doesn't correct the failure, then obviously its not GCC's builtin implementation at fault. You should be able to factor out problems with the system headers by using a test case that doesn't include at all. For example, just: int foo(char ch) { return isdigit(ch); } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18785