public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kghazi at verizon dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18785] [4.0 Regression] isdigit builtin function fails with EBCDIC character sets
Date: Thu, 02 Dec 2004 15:08:00 -0000	[thread overview]
Message-ID: <20041202150848.9234.qmail@sourceware.org> (raw)
In-Reply-To: <20041202142212.18785.darcypj@us.ibm.com>


------- Additional Comments From kghazi at verizon dot net  2004-12-02 15:08 -------
Subject: Re:  [4.0 Regression] isdigit builtin function fails with EBCDIC character sets

The .i attachments you supplied use C header macro versions of isdigit, not
the builtin function.  E.g.:

retval = ((*__ctype_b_loc ())[(int) (('3'))] & (unsigned short int)
_ISdigit);

So I don't see how this interacts with the builtin.  Were these files
generated in error?

It's possible in some cases to disable these ctype macros by supplying -D
flags, but you don't indicate that you did this in your tests.



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18785


  parent reply	other threads:[~2004-12-02 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 14:23 [Bug middle-end/18785] New: " darcypj at us dot ibm dot com
2004-12-02 14:25 ` [Bug middle-end/18785] " darcypj at us dot ibm dot com
2004-12-02 14:29 ` [Bug middle-end/18785] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-12-02 15:08 ` kghazi at verizon dot net [this message]
2004-12-02 15:27 ` darcypj at us dot ibm dot com
2004-12-02 15:56 ` kghazi at verizon dot net
2004-12-04  3:44 ` roger at eyesopen dot com
2004-12-05  3:23 ` pinskia at gcc dot gnu dot org
2004-12-06 22:06 ` kghazi at verizon dot net
2004-12-07 15:21 ` darcypj at us dot ibm dot com
2004-12-07 20:08 ` kghazi at verizon dot net
2004-12-22 16:40 ` roger at eyesopen dot com
2005-02-20 23:07 ` cvs-commit at gcc dot gnu dot org
2005-02-20 23:07 ` zack at codesourcery dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041202150848.9234.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).