public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/78155] missing warning on invalid isalpha et al.
Date: Mon, 04 May 2020 11:51:02 +0000 [thread overview]
Message-ID: <bug-78155-4-0YkITBwsJe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78155-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78155
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno at clisp dot org
--- Comment #6 from Bruno Haible <bruno at clisp dot org> ---
Created attachment 48440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48440&action=edit
Test case
Another test case is the attached program, alpha.c. When run on glibc systems
on x86, x86_64, and other CPUs (not powerpc), it sign-extends the 'char'
argument; so the character 'ÿ' (in ISO-8859-1 encoding) becomes EOF, and the
<ctype.h> function returns 0.
$ LC_ALL=de_DE.ISO-8859-1 xterm
$ ./a.out ÿ
not alphabetic
The corrected program (with a cast to 'unsigned char' in the isalpha()
argument) behaves as expected:
$ LC_ALL=de_DE.ISO-8859-1 xterm
$ ./a.out ÿ
alphabetic
next parent reply other threads:[~2020-05-04 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-78155-4@http.gcc.gnu.org/bugzilla/>
2020-05-04 11:51 ` bruno at clisp dot org [this message]
2022-04-28 11:57 ` [Bug c/78155] missing warning on invalid usage of functions/macros from <ctype.h> (isalpha et al.) egallager at gcc dot gnu.org
2022-06-08 17:39 ` egallager at gcc dot gnu.org
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=bug-78155-4-0YkITBwsJe@http.gcc.gnu.org/bugzilla/ \
--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).